About change



Thrown by the persistence provider when EntityManager.persist(Object) is called and the entity already exists.(Exception of JPA)


Doctor - high memory usage

Hi, Is it possible to reduce Doctor memory usage? Right now for recovering 67MB database, I need to set heap space to at least 450MB. Even then whole process takes ages. Optimal setting for this database is about 650MB. It's about ten times of size of database. ... exception - as you got. However, if I change the temp threshold from 64MB to 8MB: <temp path = ...


Problem on JPA Merge Entity.

Hello, I have a problem with the EntityManager.merge() function. I set a property value of an entity (statement) with an other entity (newSingleConstraint). newSingleValue is already persisted. I do this myself (no use of cascade because sometimes the newSingleValue is already in database).   The statement update don't throw exception. And when i try to reload statement the value i have set before is a null value. I check with the Explorer, the statement has a null value on the property and the newSingleValue is present.... apologies , in fact I did not change the version in the configuration file of maven ...



Thrown by the persistence provider when a problem occurs.(Exception of JPA)


Java 6/7 Performance Comparison

Hey, I've been using ObjectDB for a small scale home project to gain some familiarity before proposing it in a commercial project at work. What I've noticed though is that when using objectdb in embedded mode based on the console tutorial, there seems to be a bit of a performance gap running the same code between Java 6 & 7 Tracing it through I can see the bottle neck seems to be at the creation of the entity manager and I was wondering if there are any additional configuration options I may have missed while running under java 7. ... outputs across 2 runs of the test case. I had to change the test case slightly to include a modal JDialog which would stop the ...



Thrown by the persistence provider when a query times out and only the statement is rolled back.(Exception of JPA)



Thrown by the persistence provider when Query.getSingleResult() or TypedQuery.getSingleResult()is executed on a query and there is no result to return.(Exception of JPA)



Thrown by the persistence provider when Query.getSingleResult() or TypedQuery.getSingleResult() is executed on a query and there is more than one result from the query.(Exception of JPA)



The class Exception and its subclasses are a form of Throwable that indicates conditions that a reasonable application might want to catch.(Exception of java.langException Exception)


Unexpected exception (Error 990) com.objectdb.o.InternalException

Hello, we get an exception if we use Enhanced Entities. With not enhanced Entities we get no error. ...   Now it's really interesting: If we change the loggingLevel   from "fatal" to "warning", we get other ...