Use operation wide transactions #21

Open
opened 2024-08-06 01:28:15 +02:00 by oysteikt · 1 comment
Owner

A lot of the database operations are currently handled as single statements. In order to assist with #20 and make the tool safer to use, do all operations as a single database transaction.

A lot of the database operations are currently handled as single statements. In order to assist with #20 and make the tool safer to use, do all operations as a single database transaction.
oysteikt added the good first issuefeature request labels 2024-08-06 01:28:15 +02:00
oysteikt reopened this issue 2024-08-17 20:37:21 +02:00
Author
Owner

Note that this is not per request/response pair, rather it is per session-handler (or per client command). We need to start a transaction when the server has accepted a new socket connection and is about to wait for requests. On Request::Exit, we commit the changes to the database. If there is no Request::Exit, we rollback

Note that this is not per request/response pair, rather it is per session-handler (or per client command). We need to start a transaction when the server has accepted a new socket connection and is about to wait for requests. On `Request::Exit`, we commit the changes to the database. If there is no `Request::Exit`, we rollback
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Projects/muscl#21