Change
Autocommit off: Refactor API implementation
Issue description
The changes for auto commit off gave rise to inconsistencies in the code base.
Developer comments
The basic requirement is to apply the changes made in the API calls to both storage layers, the MySQL database for permanent persistence and to the dobjects, the in-memory representation of the data. The data change C1 caused by a modifying API call is propagated to these storage layers (MySQL and dobject) differently depding whether auto commit is on or off.
* auto commit on: C1 is written to MySQL and immediately applied to dobject.
* auto commit off: C1 is applied to dobject temporarily. Upon commit, write to MySQL and apply to dobject permanently.
|
Work sessions4
Start |
2023-02-13T09:00:00
|
End |
2023-02-13T14:41:56
|
Participant |
Robert Cerny
|
Start |
2023-02-13T21:00:00
|
End |
2023-02-13T23:00:00
|
Participant |
Robert Cerny
|
Start |
2023-02-14T07:57:15
|
End |
2023-02-14T09:28:13
|
Participant |
Robert Cerny
|
Start |
2023-02-14T09:56:22
|
End |
2023-02-14T11:21:36
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.