You should open these as bugs. The JPQL parser is very new code; I expect that we will run into a fair number of parse bugs / limitations. (OpenJPA should pass what's in the TCK, but that's hardly complete coverage.)
-Patrick -- Patrick Linskey BEA Systems, Inc. > -----Original Message----- > From: David Wisneski [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 10, 2006 12:25 PM > To: email@example.com > Subject: EJB QL grammar > > I noticed in doing some testing with OpenJPA that the > OpenJPA jjt grammar > file is not quite in sync with JPA spec. For instance > > " select NEW .... " should only be valid in top level query, not > subquery. > > " ... having max( e.salary ) ..." gives syntax error. > Expressions in > having clause should allow aggregate functions. > > " select e from Employee e where exists ( select p from > in(e.projects) > p ) " is valid EJB QL but gives syntax error. > > I have also gotten bad sql generated if a subquery contains another > subquery. > > Is anyone else aware of these or should I open up bugs. > _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.