ObjectDB ObjectDB

Internal Website Search

21-30 of 168 resultsRefresh

Pre-detach loading: retrieval by navigation not working in if statement

: objectdb.temp.no-detach NOT USED This problems only seems to occur in my large web application. I know ... and why. I am using pre-detach loading after em.find(id), because just relying on JPA-annotations ... these during the pre-detach loading should (and usually does) load everything needed to compute a transient expert

Detaching objects after JOIN FETCH

Hi, I have a question about detaching objects after issuing query with JOIN FETCH. Let's say I ... .aClasses After closing entity manager, B classes became detached but without A classes and because EM is closed, B.aClasses is always null. I thought, that after join fetch and CascadeType.DETACH list

Changes in detach behaviour?

out that all fields of retrieved objects are on their default value till i first call a getter or detach ... and the em. With 2.3.5_04 I get an empty detached user object back. Only the id is correct. Shouldn't the detach and field population happen implicitly during em.close()? mosi0815 Ralph Moser

The exception "Attempt to remove a detached entity object" have no information about the entity

Hello, the exception "Attempt to remove a detached entity object" have no information about the detached entity. It is very hard, especially if the involved entities uses cascading, to find the removed call for the detached entity. It would be very helpful if you can add a few information

Attempt to remove a detached entity object (error 613)

Hello, that's a strange error for me ... I have a detached object in my Java code and i just wanted to merge it ... Unfortunatly, i get this error : Failed to commit transaction: Attempt to remove a detached entity object (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:290) We see in

NPE after an @embedded obj is updated for a detached entity

I have an entity that looks like this: class User {     @embedded private Profile profile;     ... } After running something like this:     User user = entityManager.createQuery("select......     entityManager.detach(user);     user.getProfile().setDescription("Something... I

Retrieving JPA Entity Objects

. The fetch policy also affects objects that become detached (e.g. when the EntityManager is closed). Transparent activation is not supported for detached objects. Therefore, only content that has already been fetched from the database is available in objects that are detached. JPA 2 introduces methods

Query in nested transaction returns detached entity if lazy-loaded

Hello, we've encountered an issue with ObjectDB. The attached code is a minimal example of the relevant work flow and fails at the assert in line 58: assertTrue(secondQueryResult.get(1).strValue != null); The entity is detached and data is not loaded lazily from the database. We've also found


in this PersistenceManager. This method makes transient instances persistent and applies detached ... , the create life cycle listener is called. For detached instances, it locates or instantiates a persistent instance with the same JDO identity as the detached instance, and merges the persistent


, and the various setGroups calls. Value: default. Since: JDO 2.0 int DETACH_LOAD_FIELDS For use ... plan should be loaded prior to detachment. Since: JDO 2.0 int DETACH_UNLOAD_FIELDS For use ... should be unloaded prior to detachment. Since: JDO 2.0 int FETCH_SIZE_GREEDY For use with setFetchSize

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