Home » Search

About commit

91-100 of 200Refresh
Forum
2

Dirty checking

that were changed after a commit, i.e: after the transaction has succeeded, so that I can update views ... , and also, the entire transaction could fail. i.e: I'd really like to know after a commit what objects changed in the prior commit. in other words a 'post-commit' listener.  I can guarentee single threaded access
Forum
2

Merge Issue: Attempt to reuse an existing primary key value

("child1"));         em.merge(e1);         em.getTransaction().commit();         em.clear ... (e2);         em.getTransaction().commit();         em.clear();         em.close ... instance         em.getTransaction().commit();         a = em.createQuery(             "SELECT
Forum
2

objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation

there are now obsolete): - Issue #282 - ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric ... to commit transaction: Failed to locate set method for field property com.greensoft.objectdb.test.entity.value.EnumValue.oldValue using reflection (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java
Issue
2

Best practise loading big data

only workarounds helped to gain a lower memory footprint. One is to stupidly commit the transaction after a certain number of read accesses (every 10000 read access to commit and open a new transaction ... is not defined. Could you please repair the code? You mentioned commit as a workaround. It is unclear
JPA Doc
2

CacheStoreMode.REFRESH

Enum Constant javax.persistence.CacheStoreMode REFRESH Insert/update entity data into cache when read from database and when committed into database. Forces refresh of cache for items read from database. Since: JPA 2.0
JPA Doc
2

CacheStoreMode.USE

Enum Constant javax.persistence.CacheStoreMode USE Insert/update entity data into cache when read from database and when committed into database: this is the default behavior. Does not force refresh of already cached items when reading from database. Since: JPA 2.0
Forum
2

Date field Index is corrupted due to time change

.persistence.RollbackException Failed to commit transaction: (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:302) at com.arunta.base.db.RecordingMetaDataDAO.commitTxn ... :835) at com.objectdb.o.OBM.bL(OBM.java:740) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:299
JDO Doc
2

deletePersistent(pc)

Method javax.jdo.PersistenceManager void deletePersistent(   Object pc ) Delete the persistent instance from the data store. This method must be called in an active transaction. The data store object will be removed at commit. Unlike makePersistent, which makes the closure of the instance
JDO Doc
2

ForeignKey.deferred

Annotation Element javax.jdo.annotations.ForeignKey String deferred Whether this foreign key is deferred (constraint is checked only at commit). Returns: whether this foreign key is deferred Default value: "" Since: JDO 2.1
JDO Doc
2

getOptimistic()

Method javax.jdo.Transaction boolean getOptimistic() Optimistic transactions do not hold data store locks until commit time. Returns: the value of the Optimistic property. Since: JDO 1.0