Fast Object Database for Java - with JPA/JDO support

Internal Website Search

131-140 of 200 resultsRefresh
2

javax.persistence.EntityExistsException

is invoked, or the EntityExistsException or another PersistenceException may be thrown at flush or commit
2

setRetainValues(retainValues)

Method javax.jdo.Transaction void setRetainValues( boolean retainValues ) If true, at commit instances retain their values and the instances transition to persistent-nontransactional. If an implementation does not support this option, a JDOUnsupportedOptionException is thrown. Parameters
2

Date field Index is corrupted due to time change

) to the DB [ObjectDB 2.5.5_14] javax.persistence.RollbackException Failed to commit transaction: (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:302) at com.arunta.base.db.RecordingMetaDataDAO ... .commit(EMImpl.java:299) ... 17 more It will be beneficial to us to know if time change, in
1

Is it possible to remove parent/child entities without refresh?

.persistence.RollbackException Failed to commit transaction: (error 613)). Do you have an idea ... .addChild(new ChildEntity().withChildName("childEntity4"));   entityManager.getTransaction().commit ... ();   entityManager.remove(parentEntity.getChildren().get("childEntity1"));   entityManager.getTransaction().commit
1

Felix, rollback exception, error 613

can begin, persist and commit once, but not twice; even after framework restart. I need to delete ... to /example/ [ObjectDB 2.7.5] javax.persistence.RollbackException Failed to commit transaction: Failed ... .EMImpl.commit(EMImpl.java:289) at db.Activator.storePoints(Activator.java:34) at FelixProject
1

InternalException

Failed to commit transaction: (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:279) at rbccm.felix.objectdb.workflow.ObjectDbInstanceContainer.commit(Unknown Source) at rbccm.digest ... ) at com.objectdb.o.OBM.bG(OBM.java:719) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:276) ... 9
1

calling persist on an object more than once

results in an error (613) when the transaction is commited: [ObjectDB 2.2.4] javax.persistence.RollbackException Failed to commit transaction: Attempt to reuse an existing primary key value (common.model.UserSession:13) (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:271) at javax.jdo
1

Tracking changes to new collections (in enhancement mode) after flush

operations being performed in between. Once the transaction is committed, the issue is that the last ... ().commit();         em.clear();                  entity = em.find(ListInMap.class, id ... ); //------------------------------- //------------------------------- em.getTransaction().commit
1

OptimisticLockException

with these exceptions: [ObjectDB 2.2.5_04] javax.persistence.RollbackException Failed to commit transaction ... if locking version-check is set false? are the changes from process B lost if process A subsequently commits ... to the user if it tries to commit changes on a document that has been concurrently changed by
1

Use temporary files to enable very large transactions

We managed to add a new option of using temporary files for flush / commit, as suggested in #6 ... of this database. This enables us to repeatedly commit on the second database and in case of a fault we can still recover a consistent state. We run the commit, if the Application consumes a percentage

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support