Home » Search

About EntityManager

111-120 of 200Refresh
Forum
3

Performance in large transactions

++) { EntityManager entityManager = getEntityManagerFactory().createEntityManager(); entityManager.setFlushMode(FlushModeType.AUTO); EntityTransaction transaction = entityManager.getTransaction ... = create10000Entites(); entityManager.merge(entities); x.end += 1; transaction.commit
JPA Doc
3

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
JPA Doc
3

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
JPA Doc
3

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
Forum
3

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
Issue
3

Removing of an entity removes also another entity type

with a result and after that a ToleranceDefinition entity is removed from database by entitymanager ... . Please note that mixing direct DELETE / UPDATE database queries with EntityManager's operations is known as ... the EntityManager mechanism and therefore are very risky as the EntityManager can easily loss
Issue
3

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
Forum
3

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
Issue
3

NullPointer when accessing entity field

during the operation. This could happen when an object is accessed in one thread 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
Forum
3

Optimistic locking: prevent version increment on entity collection attribute

this must be an issue with the EntityManager's life cycle but cannot figure out what. I am using Guice injection and Guice persist and should get one EntityManager per request. Also, please note that in the web ... () {     // em is the EntityManager     em.getTransaction().begin();        Document doc = new