Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

put database operations in a queue and submit in one strike #59

Open
briansalehi opened this issue Mar 3, 2023 · 0 comments
Open

put database operations in a queue and submit in one strike #59

briansalehi opened this issue Mar 3, 2023 · 0 comments
Assignees

Comments

@briansalehi
Copy link
Owner

Any user change attempt should be saved offline in an operation queue.
This is useful for reducing database connections, specially when application
loses connection between practice and user keeps practicing without interrupts.

Operations should be saved locally, in case program crashes or any other interruption
occurs.

@briansalehi briansalehi self-assigned this Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant