|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
Yes, this problem is causing me a lot of heartburn. I am using Sybase which pukes on column aliases inside a subquery. I was trying to get around this with:
subquery1.setProjection(Projections.sqlProjection("1", null, null)); // causes NullPointerException
or by not using a projection at all. // causes NullPointerException
I, too, am using Subqueries.exists(). // projection shouldn't be needed
Every valid projection I set on the subquery (even a rowCount) results in a column alias which Sybase cannot handle.
Newly added: We brought up a new server with Sybase ASE 15.7 which does NOT puke on column aliases inside a subquery. I can use the Criteria API with DetachedCriteria subqueries now.
For those Sybase users who haven't upgraded to ASE 15.7:
this worked for me--
subquery1.setProjection(Projections.sqlProjection("*", new String[]{"value"}, new Type[]{new StringType()}));