Created: (JBSEAM-2302) Query Parser adding Where clause conditions t

Query Parser adding Where clause conditions to Non Where
clauses
------------------------------------------------------------
----

                 Key: JBSEAM-2302
                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2302
             Project: JBoss Seam
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.2.1.GA
         Environment: Any
            Reporter: Terry


When using EntityQuery's getEjbql() and getRestrictions()
override methods; and if ejbql in getEjbql() contains any
clause after the WHERE clause - such as GROUP BY, the query
parses appends restrictions to GROUP BY clause rather than
to the WHERE clause.

It seems, that EntityQuery expects WHERE to be last clause
in ejbql.



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

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es

     [ http://jira.jboss.com/jira/browse/JBSEAM-2302?page=all
]

Pete Muir updated JBSEAM-2302:
------------------------------

    Fix Version/s: 2.0.2.GA

> Query Parser adding Where clause conditions to Non
Where clauses
>
------------------------------------------------------------
----
>
>                 Key: JBSEAM-2302
>                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2302
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.1.GA
>         Environment: Any
>            Reporter: Terry
>             Fix For: 2.0.2.GA
>
>
> When using EntityQuery's getEjbql() and
getRestrictions() override methods; and if ejbql in
getEjbql() contains any clause after the WHERE clause - such
as GROUP BY, the query parses appends restrictions to GROUP
BY clause rather than to the WHERE clause.
> It seems, that EntityQuery expects WHERE to be last
clause in ejbql.

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

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es

     [ http://jira.jboss.com/jira/browse/JBSEAM-2302?page=all
]

Norman Richards reassigned JBSEAM-2302:
---------------------------------------

    Assignee: Norman Richards

> Query Parser adding Where clause conditions to Non
Where clauses
>
------------------------------------------------------------
----
>
>                 Key: JBSEAM-2302
>                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2302
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.1.GA
>         Environment: Any
>            Reporter: Terry
>         Assigned To: Norman Richards
>             Fix For: 2.0.2.GA
>
>
> When using EntityQuery's getEjbql() and
getRestrictions() override methods; and if ejbql in
getEjbql() contains any clause after the WHERE clause - such
as GROUP BY, the query parses appends restrictions to GROUP
BY clause rather than to the WHERE clause.
> It seems, that EntityQuery expects WHERE to be last
clause in ejbql.

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

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es

     [ http://jira.jboss.com/jira/browse/JBSEAM-2302?page=all
]

Norman Richards closed JBSEAM-2302.
-----------------------------------

    Fix Version/s: 2.1.0.GA
                       (was: 2.0.2.GA)
       Resolution: Done

Added groupBy property to queries so Seam can do the right
thing here.

> Query Parser adding Where clause conditions to Non
Where clauses
>
------------------------------------------------------------
----
>
>                 Key: JBSEAM-2302
>                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2302
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.1.GA
>         Environment: Any
>            Reporter: Terry
>         Assigned To: Norman Richards
>             Fix For: 2.1.0.GA
>
>
> When using EntityQuery's getEjbql() and
getRestrictions() override methods; and if ejbql in
getEjbql() contains any clause after the WHERE clause - such
as GROUP BY, the query parses appends restrictions to GROUP
BY clause rather than to the WHERE clause.
> It seems, that EntityQuery expects WHERE to be last
clause in ejbql.

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

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es