From open-jpa-dev-return-466-apmail-incubator-open-jpa-dev-archive=incubator.apache.org@incubator.apache.org Tue Aug 22 21:21:29 2006 Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 73602 invoked from network); 22 Aug 2006 21:21:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Aug 2006 21:21:29 -0000 Received: (qmail 43487 invoked by uid 500); 22 Aug 2006 21:21:29 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 43417 invoked by uid 500); 22 Aug 2006 21:21:29 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 43408 invoked by uid 99); 22 Aug 2006 21:21:29 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Aug 2006 14:21:29 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of kwsutter@gmail.com designates 64.233.184.233 as permitted sender) Received: from [64.233.184.233] (HELO wr-out-0506.google.com) (64.233.184.233) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Aug 2006 14:21:28 -0700 Received: by wr-out-0506.google.com with SMTP id i5so450259wra for ; Tue, 22 Aug 2006 14:21:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=SUldIW0Q0lMn/Hh0xJaRUFORHkwLGU2n0P0lkIz98EyvwaG3tAv4p7Kt3o4so58DjK1x4h79zdJZ6fnbyan0lK87gCvI+ccpUaY+lQ6+RKPwLdLh6ESC/mIHEZDesQBmHMAn+Dkyjiz4PxrRrd6cUvosyTT90dyEBnfHp3ulG8g= Received: by 10.90.54.4 with SMTP id c4mr684410aga; Tue, 22 Aug 2006 14:21:07 -0700 (PDT) Received: by 10.90.86.14 with HTTP; Tue, 22 Aug 2006 14:21:07 -0700 (PDT) Message-ID: <89c0c52c0608221421uc019041ge7dfc521ba5a6b67@mail.gmail.com> Date: Tue, 22 Aug 2006 16:21:07 -0500 From: "Kevin Sutter" To: open-jpa-dev@incubator.apache.org Subject: Re: [jira] Updated: (OPENJPA-15) EJBQL grammar needs to be updated to relfect JPA specification In-Reply-To: <151413.1156280714311.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_16806_2229677.1156281667365" References: <32785404.1155768493817.JavaMail.jira@brutus> <151413.1156280714311.JavaMail.jira@brutus> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_16806_2229677.1156281667365 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Now that we have successfully created a patch for OPENJPA-15, what is the process for getting this validated and hopefully accepted into SVN? I have been able to verify that the patch can be applied, everything builds, and the existing testcases still work. But, I'm not an expert with the code that is being updated, so it would be good for another committer to verify the changes. Thanks! Kevin On 8/22/06, Catalina Wei (JIRA) wrote: > > [ http://issues.apache.org/jira/browse/OPENJPA-15?page=all ] > > Catalina Wei updated OPENJPA-15: > -------------------------------- > > Attachment: OPENJPA-15.openjpa-kernel.txt > > This patch is applied successfully against openjpa-kenel. > please ignore the previous attachments. > > > 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 > > Attachments: OPENJPA-15.openjpa-kernel.txt, OPENJPA-15.txt > > > > > > 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 > > > ------=_Part_16806_2229677.1156281667365--