15 | Performance in large transactions.) Pseudocode for the fast and the slow solution FAST: for (i = 0; i <100; i ++) { EntityManager entityManager = getEntityManagerFactory().createEntityManager(); entityManager.setFlushMode(FlushModeType.AUTO); EntityTransaction transaction = entityManager.getTransaction |
15 | @OneToMany(fetch = FetchType.LAZY) list is always null") private EntityManager entityManager; @EJB private Manager manager; private ... = entityManager.createQuery("SELECT p FROM Parent p"); parents = query.getResultList ... (unitName = "my-pu") private EntityManager entityManager; public void persist(Object o |
14 | Memory Leaks after COMMIT operation (checked on versions 2.6.5 & 2.6.6.b01)_EntityManager = m_EntityMgrFactory.createEntityManager(); m_EntityManager.setFlushMode( FlushModeType.COMMIT ); if ( m_EntityManager.isOpen() ) { m_EntityManager.getTransaction().begin(); for ( Pa3DataKey dataKey : aDataKeys ) { m_EntityManager.persist( dataKey |
12 | Weird behaviour with enhanced classes and embedded entities.persistence.EntityManager; import javax.persistence.EntityManagerFactory; import javax.persistence ... ){ this.title = title; } } private static EntityManager entityManager; public ... .createEntityManagerFactory("objectdbsscce.odb"); entityManager = entityManagerFactory |
2 | javax.persistence.NamedNativeQuery name The name used to refer to the query with the EntityManager methods that create query objects. The name used to refer to the query with the EntityManager methods that create query objects |
2 | javax.persistence.Persistence: persistenceUnitName - the name of the persistence unit Returns: the factory that creates EntityManagers configured ... : the factory that creates EntityManagers configured according to the specified persistence unit. Since: JPA 1.0 |
2 | javax.persistence.EntityExistsException: Serializable Thrown by the persistence provider when EntityManager.persist(Object) is called ... See Also: javax.persistence.EntityManager.persist(Object) EntityExistsException() Constructs a new |
2 | Removing of an entity removes also another entity type with a result and after that a ToleranceDefinition entity is removed from database by entitymanager ... / UPDATE database queries with EntityManager's operations is known as problematic. It is not specific to ObjectDB but general to JPA. DELETE / UPDATE JPA queries bypass the EntityManager mechanism |
2 | Remove of an entry from a @OneToMany collection is not possible if the enhancer is disabled.persistence.EntityManager; import javax.persistence.EntityManagerFactory; import javax.persistence ... /test.tmp;drop"); EntityManager entityManager = emf.createEntityManager(); ParentEntity parentEntity = new ParentEntity(); entityManager.getTransaction().begin(); entityManager.persist |
2 | NullPointer when accessing entity field while the EntityManager is manipulated concurrently in another thread (e.g. transaction is committed or the EntityManager is closed). Is it possible that an EntityManager and/or its managed objects were accessed concurrently by more than one thread? support Support We are using EntityManagers in following |
