Home » Search

About commit

31-40 of 200Refresh
Forum
20

Query problem after transaction commit

.begin ... persist(p) .. commit of a new object, my client program can no longer retrieve the old ... with a simple solution (e.g. changing flush mode from commit to auto could solve it). However, a situation
Issue
20

Error on commit

I get the following on commit:  (v2.3.7_15) Let me know if you need more info. Caused by: com.objectdb.o.InternalException at com.objectdb.o.InternalException.f(InternalException.java:236) [:] at com.objectdb.o.SPW.aq(SPW.java:109) [:] at com.objectdb.o.PGW.am(PGW.java:210) [:] at com
Forum
20

Failed to commit transaction: Java heap space (error 613)

.RollbackException Failed to commit transaction: Java heap space (error 613) We are using ObjectDB 2.4.6_10
Forum
20

Need to close+open database for a commit to be taken into account

Hi, I have one case where commit (update of entity in this case) is not taken in account unless database is actually closed and re-open, no error. I tried to use flush instead of close+re-open but it does not work. So currently there is a dirty close + open + reload on each update
Forum
20

Query and commit simultaneously

Is it possible to query and commit on the same persistence manager (i.e. same odb file) at the same time? Multithreading is fully supported by ObjectDB, so you can query and update the database at the same time using multiple threads. However, if all the threads share the same EntityManager
Forum
20

StackOverflowError after commit

We have following issue, if we execute a commit: java.lang.StackOverflowError at com.objectdb.o.ENT.D(ENT.java:411) at com.objectdb.o.ENT.D(ENT.java:499) at com.objectdb.o.ENT.D(ENT.java:417) at com.objectdb.o.ENT.D(ENT.java:499) at com.objectdb.o.ENT.D(ENT.java:499) at com.objectdb.o.ENT.D
Manual
20

Locking in JPA

separately. Optimistic locking is applied on transaction commit. Any database object ... is being performed on an old version of a database object, for which another update has already been committed ... must be revealed earlier (before transaction commit) pessimistic locking can be used. When using
Manual
20

Setting and Tuning of JPA Queries

em can be visible to anyone who uses em, even before committing the transaction (but not to users ... , which has two values: AUTO - changes are flushed before query execution and on commit/flush. COMMIT - changes are flushed only on explicit commit/flush. In most JPA implementations the default is AUTO. In
Forum
19

Git seems not to commit objectdb.conf

Git seems not to commit objectdb.conf
Manual
15

Auto Generated Values

id; : } During a commit the AUTO strategy uses the global number generator to generate ... also generates an automatic value during commit for every new entity object. The difference is that a separate ... is persisted (i.e. before commit). This may be useful when the primary key value is needed earlier