About jpql

release

2.6.4

... Fixed processing an IN(:param) expression in JPQL queries. Version 2.5.0 Added support of nested ... issue #125 ). Fixed a bug in using JPQL operations (e.g. UPPER ) in DISTINCT results. Fixed ...

 
release

2.4.4

... issue #125 ). Fixed a bug in using JPQL operations (e.g. UPPER ) in DISTINCT results. Fixed ... Added support of IN operator in JPQL queries. Added support of ";drop" database url ... support of navigation through collections  (as a JPQL extension). Added version display to the Server and Explorer ...

 
release

2.6.5

... Fixed processing an IN(:param) expression in JPQL queries. Version 2.5.0 Added support of nested ... issue #125 ). Fixed a bug in using JPQL operations (e.g. UPPER ) in DISTINCT results. Fixed ...

 
release

2.6.6

... Fixed processing an IN(:param) expression in JPQL queries. Version 2.5.0 Added support of nested ... issue #125 ). Fixed a bug in using JPQL operations (e.g. UPPER ) in DISTINCT results. Fixed ...

 
release

2.4.3

... issue #125 ). Fixed a bug in using JPQL operations (e.g. UPPER ) in DISTINCT results. Fixed ... Added support of IN operator in JPQL queries. Added support of ";drop" database url ... support of navigation through collections  (as a JPQL extension). Added version display to the Server and Explorer ...

 
forum_thread

First query takes 4+ minutes to complete

Hi, we are evaluating ObjectDB 2.5.1_04 in embedded mode hoping to replace SQLite in our application. We observed that in our case it takes on average more than 4 minutes to complete the first SELECT query that we run on the DB which contains about 320,000 records of a single type of object. SQLite in comparison responds within few seconds on average with the same number of records. We hope to receive your recommendation on how to improve this result with this post.   Test System ... 2. The 2nd EntityManager runs the queries (JPQL SELECT statements) shown next.  Query We test ... good for fields that appear in the WHERE part of the SQL/JPQL. In our case the fields are in the ORDER part. So, I do not think an index ...

 
release

2.6.2

... Fixed processing an IN(:param) expression in JPQL queries. Version 2.5.0 Added support of nested ... issue #125 ). Fixed a bug in using JPQL operations (e.g. UPPER ) in DISTINCT results. Fixed ...

 
release

2.6.3

... Fixed processing an IN(:param) expression in JPQL queries. Version 2.5.0 Added support of nested ... issue #125 ). Fixed a bug in using JPQL operations (e.g. UPPER ) in DISTINCT results. Fixed ...

 
release

2.4.2

... issue #125 ). Fixed a bug in using JPQL operations (e.g. UPPER ) in DISTINCT results. Fixed ... Added support of IN operator in JPQL queries. Added support of ";drop" database url ... support of navigation through collections  (as a JPQL extension). Added version display to the Server and Explorer ...

 
release

2.4.1

... issue #125 ). Fixed a bug in using JPQL operations (e.g. UPPER ) in DISTINCT results. Fixed ... Added support of IN operator in JPQL queries. Added support of ";drop" database url ... support of navigation through collections  (as a JPQL extension). Added version display to the Server and Explorer ...