[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1944) generated subqueries and jpaql compliance (derived select clause) check

[Steve Ebersole (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1944?page=all ]

Steve Ebersole updated HHH-1944:
--------------------------------

    Summary: generated subqueries and jpaql compliance (derived select clause) check  (was: JPA compliance complains when  IS EMPTY is used)

> generated subqueries and jpaql compliance (derived select clause) check
> -----------------------------------------------------------------------
>
>          Key: HHH-1944
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1944
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.2.0.cr3
>     Reporter: Emmanuel Bernard
>     Assignee: Steve Ebersole
>     Priority: Blocker
>      Fix For: 3.2.0.ga

>
>
> is empty is actually translated by the AST into a subtree having an implicit select clause
> On my version I've check that we're at level 1 before raising the exception. This might not be the perfect fix
> if ( getSessionFactoryHelper().isStrictJPAQLComplianceEnabled() && fromClause.getLevel() == 1 ) {
> 	throw new QuerySyntaxException( "JPA-QL compliance requires select clause" );
> }

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