ObjectDB ObjectDB

Internal Website Search

71-80 of 200 resultsRefresh

Populating entity id before transaction commit

Hi, I have a question about populating auto generated id before transaction commit. We are using OBD with Spring and transactions are managed by Spring. The problem is, that we have custom annotation ... transaction is committed so all returned entities are not populated with ID in this context. How can I

Update entity without first opening a transaction

Hi everyone, I want to update an entity in my program without having to open a transaction, do the modifications and commit the transaction. I want to have a managed entity that is in sync ... transactions for updating the content of a database. But if you use Java EE or Spring, the container may manage the transactions automatically. support Support

Query for objects persisted within the same transaction

I have a question concerning reading uncommited entities with query, within active transaction. For example, I read data from file. Each line contains value of one of entity's attributes ... and persisted withing current transaction is invisible to future queries in this transaction, unless

Is it possible to using JDO and distributed transaction?

I'am new to study JDO. Can and How I use JDO an distributed transaction?(multiple database ... Documentation JCA, JTA, and JDO Transactions - Using and Understanding Java Data Objects JDO : Usage of DataNucleus within a JEE environment btpka3 ZhangLiangLiang ObjectDB supports distributed transactions

remove & persist in same transaction => Attempt to reuse an existing primary key value

transaction: first remove additional Data -> The special Entity (with id 1) is empty and we remove ... an entity object and then in the same transaction persisting another object with the same primary key

ODB-FileWriter holds unecessary entity reference after transaction and entity manager are closed

a transaction (including the entity manager) the ODB file writer still holds a reference to entities ... DBVectorStepBlockCollectionImpl was modified and then the transaction will be committed. em.getTransaction ... much memory, if we execute several transactions on the identical entity manager. Also triggering

Unexpected exception (Error 990) - Merge with no Transaction

I am frequently having an error when merging a detached object outside of a transaction ... transaction when NontransactionalWrite is disabled: com.fastmodel.fastplan.db.experiments.ErrorTest ... with no active transaction when NontransactionalWrite is disabled: com.fastmodel.fastplan.db.experiments

Persist & remove in same transaction

I have a test case (attached) which performs the following actions: Open a new transaction Create & persist a simple entity object, EntityManager is flushed, Transaction is not committed Count ... Remove the entity object, EntityManager is flushed & cleared, Transaction is not committed Count

Inefficient memory usage with very large transactions

When a large transaction is committed, ObjectDB increases some internal structures, i.e. allocates more memory, but from that point the structures remain big and the memory is not released even if all the next transactions are small. This problem was found during a heap analysis (see #9 in

Error in production. Failed to commit transaction: Unexpected database state: BTree -152 is not found

.Read .doGet (115 ): Failed to commit transaction: Unexpected database state: BTree -152 is not found [ObjectDB 2.5.5] javax.persistence.RollbackException Failed to commit transaction: Unexpected

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