Skip to content
This repository has been archived by the owner on Sep 23, 2019. It is now read-only.

Database syncronization #108

Open
timothyhollabaugh opened this issue Sep 14, 2019 · 0 comments
Open

Database syncronization #108

timothyhollabaugh opened this issue Sep 14, 2019 · 0 comments
Labels
priority-medium Required, but does not need to happen right now scope-small A relativly small change, does not change any architecture

Comments

@timothyhollabaugh
Copy link
Member

The server creates a new thread for each request. Database access right now is not synchronized between requests. This can cause some funny business to happen, especially when the server is loaded and requests take a while. For example, if a test is submitted, but the registration is removed after the submit function checks for the registration but before it finishes grading the test. It would probably be best to use SQL row locks to ensure each item in the database is only touched by one request at a time.

@timothyhollabaugh timothyhollabaugh added the priority-medium Required, but does not need to happen right now label Sep 14, 2019
@timothyhollabaugh timothyhollabaugh added scope-medium A change that requires a bit of work, but does not significantly change the archecture scope-small A relativly small change, does not change any architecture and removed scope-medium A change that requires a bit of work, but does not significantly change the archecture labels Sep 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority-medium Required, but does not need to happen right now scope-small A relativly small change, does not change any architecture
Projects
None yet
Development

No branches or pull requests

1 participant