[hibernate-issues] [Hibernate-JIRA] Commented: (EJB-323) Lack of JPQL support for boolean literals

[Bob Tiernay (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/EJB-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_28921 ] 

Bob Tiernay commented on EJB-323:
---------------------------------

After checking the NBF, boolean literals would seem to not apply to constructor expressions.

However, hibernate currently supports integer literals in constructor expressions. At the very least the behavior should be consistent.  

I also see this as a shortcoming of the jpa spec, but that's another matter entirely :)

> Lack of JPQL support for boolean literals
> -----------------------------------------
>
>                 Key: EJB-323
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-323
>             Project: Hibernate Entity Manager
>          Issue Type: Bug
>    Affects Versions: 3.3.1.GA
>         Environment: Hibernate 3.3.1.GA / Oracle 10g
>            Reporter: Bob Tiernay
>            Priority: Minor
>
>  
> It appears as though Hibernate 3 does not support boolean literals in the select list as required by the JPA spec: 
> http://e-docs.bea.com/kodo/docs41/full/html/ejb3_langref.html#ejb3_langref_lit 
> "The boolean literals are TRUE and FALSE. Although predefined reserved literals appear in upper case, they are case insensitive" 
> Thus, JPQL queries such as: 
> "SELECT TRUE FROM Entity e" 
> Will not parse. A more realistic example is the following: 
> "SELECT NEW ValueClass(e.x, e.y, TRUE) FROM Entity e" 
> Which also does not parse. 

-- 
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