91 | Access entity version before commit transaction commiting the transaction: 1. Change entity field e.g. from a to b 2. Create a change entry in database ... the transaction before commiting it. How can I achieve this? If I add something to a collection field ... field it doesn´t. I tried transaction.flush() in combination with transaction.refresh(entity |
21 | Storing JPA Entity Objects and changes its state to Managed. The new entity object is stored in the database when the transaction ... field values). A TransactionRequiredException is thrown if there is no active transaction when persist is called because operations that modify the database require an active transaction. If the database |
21 | Database Connection using JPA the content of a database require active transactions. Transactions are managed by an EntityTransaction ... ) must be performed within an active transaction. The EntityTransaction interface represents and manages database transactions. Every EntityManager holds a single attached EntityTransaction instance |
21 | Locking in JPA separately. Optimistic locking is applied on transaction commit. Any database object ... by another transaction. When using ObjectDB, optimistic locking is enabled by default and fully ... must be revealed earlier (before transaction commit) pessimistic locking can be used. When using |
18 | Use temporary files to enable very large transactionsWe have transactions in which many objects are created. These objects are no longer needed in the current transaction after creation. Unfortunately, we will receive an OutOfMemory exception ... .com/database/forum/921 on post #4 you wrote, that ObjectDB should support very large transactions in |
18 | CRUD Database Operations with JPA) require an active transaction. In the example above, every Point object is first constructed as an ordinary Java object. It then becomes associated with an EntityManager and with its transaction (as ... only when the transaction is committed. The Storing Entities section in chapter 3 discusses |
17 | Removed entities can be found by query in the same transactionHello, we opened a transaction, load an entity from database and removed this entity by em.remove ... in build 2.7.4_04: ObjectDB uses snapshots in order to isolate transactions, i.e. to hide uncommitted flush changes of one transaction from other transactions, but still make them available |
2 | javax.jdo.JDOEntityManager. This method has no effect if a transaction is not active. If a datastore transaction is active ... transaction is active, this method obtains a datastore connection and verifies the consistency ... query is found to be invalid Since: JPA 2.0 Transaction currentTransaction() Return the Transaction |
1 | [ODB1] Chapter 9 - ObjectDB Explorer these menus. Saving Changes The Explorer manages an active transaction for every open database file ... , etc.) are stored in memory, associated with the active transaction. The "File | Save" menu command (and the equivalent toolbar button) commits the transaction which applies all the changes |
1 | javax.jdo.PersistenceManager application components. It is the factory for Query and Transaction instances, and contains methods ... if a transaction is not active. If a datastore transaction is active, this method verifies the consistency ... if flush were called, but it is not required to do so. If an optimistic transaction is active, this method |
