About jpql

release

2.3.5

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

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

... support of navigation through collections  (as a JPQL extension). Added version display to the Server and Explorer ... a bug in using fields of embedded primary key in JPQL queries. Version 2.0.3 Added support ...

 
release

2.3.6

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

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

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

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

 
issue

Issue with DISTINCT Select

It is getting more and more frustrating :( We've introduced distinct select instead of regular selection in our code (no changes else) and suddenly receive invalid identifiers in queries exceptions in various queries. Here's the stacktrace: ... because the generated code from criteriaquery is NOT valid JPQL) -> you get the same issue.   thanks for any ... I so much often wish to have a better interface than JPQL :( Thanks, Alex ...

 
release

2.4.7

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