ObjectDB ObjectDB

Internal Website Search

121-130 of 200 resultsRefresh
3

@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
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

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

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

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
2

Selective merge/cascade of detatched entity

to: EntityManager em = emf.getEntityManager(); em.getTransaction().begin(); Company company = new Company("new ... : EntityManager em = emf.getEntityManager(); em.getTransaction().begin(); Company company = new Company("new ... .createEntityManagerFactory("objectdb:/var/tmp/points.tmp;drop"); EntityManager e = emf.createEntityManager(); e

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