About HAVING

issue

query.getResultList() throws ClassCastException

I modified the example code to include an index on the Point class like so:     @Index(members={"x","y"}) Then when I run the following query:     TypedQuery<Point> query = em.createQuery("SELECT p FROM Point p where p.x <= :x and p.y >= :y",         Point.class); I get the exception at the end.  I do not get an exception if I: Bug Version: 2.3.0 Priority: Normal Status: Fixed Replies: 3 Type:  Bug ...

 
api-jpa

javax.persistence.PersistenceException

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

 
api-jpa

javax.persistence.EntityExistsException

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

 
api-jpa

javax.persistence.PessimisticLockException

Thrown by the persistence provider when an pessimistic locking conflict occurs.(Exception of JPA)

 
issue

JDO PersistenceManager.getSequence() returns null sometimes

When using JDO without annotations, database sequences are normally defined in the ORM file. Following discussion on the forum I was told that ObjectDB supports sequences if specified in the JDO file. Unfortunately, it doesn't seem to be supported consistently. It appears to work only in the situation that a new odb file has just been created AND something has been persisted to it. If nothing has yet been persisted, or if the odb file is not newly created, getSequence() returns null. Code to reproduce: Bug Version: 2.4.7 Priority: Normal Status: Fixed Replies: 5 Type:  Bug ...

 
api-jpa

javax.persistence.QueryTimeoutException

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

 
doc

java.lang.Exception

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)

 
forum_thread

OutOfMemoryError on search after update on DB created with DB Doctor

It looks like there may be an issue with the DB files created with DB Doctor in recovery mode. This is the scenario that results in the OutOfMemory exception problem (using Object DB 2.5.4_04): 1. We instruct Object DB to create a 1Gb DB file on initial start-up using: <database> <size initial="1024mb" resize="256mb" page="2kb" /> This happens as expected. #1 2014-03-11 01:36 It looks like there may be an issue with the DB files created with DB Doctor in recovery mode. This is the scenar ...

 
issue

Page cache File handling produced an java.io.IOException: Negative seek offset

we get following exception when we execute a find() in a scenario, we can not readjust with an example.   Before the exception throws we get two outputs on std error: pos = -8192 length = 8192   The Exception: Bug Version: Priority: Critical Status: Fixed Replies: 9 Type:  Bug ...

 
api-jpa

javax.persistence.NonUniqueResultException

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)