Hi,
I cannot access INF, so I send an email to the persistence alias. I will
add an INF notice for this checkin as soon as I can.
today I checked in a EJB QL compiler change fixing the EXISTS subquery
problem with an InvalidQueryKeyException thrown for an EJB QL EXISTS
subquery:
SELECT c FROM Customer c WHERE EXISTS (
SELECT o.totalPrice FROM c.orders o WHERE o.totalPrice > 99.0)
I changed the code in EJB QL ParseTree in case the FROM clause of the
subquery defines an identification variable on a collection relationship
field, such as c.order o in the above example. Now it takes the
reference class of 'c' and its ExpressionBuilder for the subquery.
The corresponding glassfish issues are:
https://glassfish.dev.java.net/issues/show_bug.cgi?id=140
https://glassfish.dev.java.net/issues/show_bug.cgi?id=365
Reviewed by: Gordon Yorke
Tests : entity-persistence-tests, local tests
The following file in the entity-persistence module is involved:
M src/java/oracle/toplink/essentials/internal/parsing/ParseTree.java
cvs commit output:
Checking in
src/java/oracle/toplink/essentials/internal/parsing/ParseTree.java;
new revision: 1.17; previous revision: 1.16
Regards Michael
--
Michael Bouschen Tech_at_Spree Engineering GmbH
mailto:mbo.tech@spree.de http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin