Yes, I stumbled on this work-around.

Nevertheless, this form of the query should:

A) Just work, or

B) Barring it just working, produce an error message from the HQL translation layer, rather than producing SQL that the database cannot handle.

Further, despite the documentation saying that SELECTs cannot work this way, they do. So there is an API inconsistency there.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira