I am using Ucanaccess-3.0.2 with JPA (EclipseLink). For most use cases it works just fine.
But I have one scenario in which I
- start a transaction,
- update a row,
- commmit the transaction,
- start a new transaction
- update the same row again
- commmit the 2nd transaction.
At that point the data from the 2nd transaction is visible upon querying (in a new transaction), but if I close EntityManagerFactory and open the MDB the 2nd transaction hasn't been persisted.
Is this possibly because the change has been made to the intermediary HSQL DB and has not yet been written to the MDB?
If so, how do I ensure that the transaction is pushed to the MDB?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi William, pay attention, you have to close/reopen ms access to see data persisted. If a commit has been called on ucanaccess, this always flushes and persists data on the access database.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am using Ucanaccess-3.0.2 with JPA (EclipseLink). For most use cases it works just fine.
But I have one scenario in which I
- start a transaction,
- update a row,
- commmit the transaction,
- start a new transaction
- update the same row again
- commmit the 2nd transaction.
At that point the data from the 2nd transaction is visible upon querying (in a new transaction), but if I close EntityManagerFactory and open the MDB the 2nd transaction hasn't been persisted.
Is this possibly because the change has been made to the intermediary HSQL DB and has not yet been written to the MDB?
If so, how do I ensure that the transaction is pushed to the MDB?
Hi William, pay attention, you have to close/reopen ms access to see data persisted. If a commit has been called on ucanaccess, this always flushes and persists data on the access database.
This issue is also being addressed on Stack Overflow here:
http://stackoverflow.com/q/34250537/2144390