Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Message-ID: <2892380.1156450689447.JavaMail.jira@brutus>
Date: Thu, 24 Aug 2006 13:18:09 -0700 (PDT)
From: "Kevin Sutter (JIRA)" <jira@apache.org>
To: open-jpa-dev@incubator.apache.org
Subject: [jira] Updated: (OPENJPA-15) EJBQL grammar needs to be updated to
 relfect JPA specification
In-Reply-To: <32785404.1155768493817.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/OPENJPA-15?page=all ]

Kevin Sutter updated OPENJPA-15:
--------------------------------

    Attachment:     (was: OPENJPA-15.openjpa-kernel.txt)

> EJBQL grammar needs to be updated to relfect JPA specification
> --------------------------------------------------------------
>
>                 Key: OPENJPA-15
>                 URL: http://issues.apache.org/jira/browse/OPENJPA-15
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: query
>            Reporter: David Wisneski
>         Assigned To: Catalina Wei
>
> when used in subquery, SELECT has different grammar than in top most query.  SELECT NEW is not allowed.  FROM in subuqery has different syntax than in top most query.  For example    "FROM d.employees as e " in subquery where it would be invalid in top query.   Expression syntax in HAVING clause needs to allow  "HAVING min(e.salary) > 10 " is valid  provided that e.salary is a grouping field.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira