ObjectDB ObjectDB

Internal Website Search

61-70 of 200 resultsRefresh

Accessing objects to make them available after EntityManager close?!

"); EntityManager em = emf.createEntityManager(); TypedQuery<Vifr_dic> query = em.createQuery("SELECT w ... objects? Many thanks mmmndt2015 Thi Nguyen Closing the EntityManager changes the state of the managed ... when the EntityManager when it was open are available (and references to unloaded objects are null). Accessing

Issue with orphanRemoval and multiple EntityManagers

with orphanRemoval set to true. I use a new EntityManager for each transaction (which normally happens in ... , the database contains 3 child entities. If I use the same EntityManager for both transactions ... @contextspace.com"));         EntityManager em = emf.createEntityManager();         em

Suspected memleak caused by bad state of EntityManager

Our application manages the Entities itself, so we close the EntityManager after every creating ... and finalize, we found the problem is caused by bad state of EntityManager. After first throwing the InternalException, the EntityManager throws every time when doing merge operation, but it can be closed

creating EntityManager on odb file created on Mac 64bit on Windows 32bit

an EntityManagerFactory and later EntityManager on this file, every thing is working fine. But, when I transfer this program and odb file to Windows XP 32bit it crashes while creating EntityManager ... EntityManager on this odb file. And the program is creating 1kb file named SMMD.org$, when the database is in

EntityManager to closed

Hi I understand we should close the entitymanager after each use, and close the factory ... . I am just running some test cases and opened up 100 entitymanager via factory.createEntityManager ... closing EntityManager and EntityManagerFactory instances is mainly wasted resources on the client side. support Support

Metamodel Attribute NOT EQUALS to same Attribute in a different EntityManager

from Metamodel of a differente EntityManager initialized on a @Controller @RequestMapping event. I ... is it: If I have two moments of initialization of "javax.persistence.metamodel" from EntityManager and these two metamodels come from different EntityManagers. One of these is on a @PostConstruct event

EntityManager getMetamodel() causes crash

I am trying to track down some obscure errors with multi-threading. This involved looking at the EntityManager Metamodel but this caused an ObjectDB exception. So I reverted to your example code in ... " EntityManager em = emf.createEntityManager(); em.getTransaction().begin

Eclipse4 RCP - No Persistence provider for EntityManager

.PersistenceException: No Persistence provider for EntityManager I'm using the latest ObjectDB 2.6.2.b03 ... an EntityManagerFactory to building an EntityManager) it may be because resources that are needed by

EntityManager.refresh takes a long time

EntityManager.refresh takes a long time for entity object Person in this code:     logger.log(Level.INFO, "begin select for person " + new Date().toString());                TypedQuery<Person ... understand this term correctly, if try to refresh Entitymanager updates only objects in his context

An entityManager.flush() with many entities is not possible

The following exception occures if we call entityManager.flush() where the corresponding JPA PersistenceContext has many entities and relations. What is the reason for the exception? entityManager.getTransaction().commit() instead of a entityManager.flush() works correctly. Unfortunately I have not

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