You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had performed some operations in a transaction which I then committed (inside the transaction I could also query the rows I just inserted), however after having committed the transaction (through DORM / rorm-lib), nothing was actually written to disk. The data was also not there when the app finished.
Got it reproducing. When just using db instead of a transaction, the data gets written to disk properly.
I had performed some operations in a transaction which I then committed (inside the transaction I could also query the rows I just inserted), however after having committed the transaction (through DORM / rorm-lib), nothing was actually written to disk. The data was also not there when the app finished.
Got it reproducing. When just using db instead of a transaction, the data gets written to disk properly.
rorm-lib call trace
The text was updated successfully, but these errors were encountered: