Criteria subquery without projection fails throwing NullPointerException
Activity
Jan SchattemanSeptember 23, 2022 at 2:23 PM
This issue has been rejected since the Hibernate legacy Criteria API was deprecated in 5.x and removed in 6.0. There will be no further development for it.
Chris WallaceSeptember 24, 2012 at 9:53 PMEdited
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()}));
Joachim DurchholzNovember 7, 2011 at 7:37 PM
This is particularly annoying since SubqueryExpression#createAndSetInnerQuery's method comment indicates that this is just prefetching data that it assumes will be needed later.
And, yes, it just bit me. And I'm not going to comment on how long this has been lying dormant.
Assaf BergJanuary 23, 2006 at 6:11 PM
Same here. This is extremely annoying, especially since i'm using Subqueries.exists(), which means the projection isn't really relevant.
In the very least this should throw a more informative exception. Probably it would be better if there would be a default projection set (like Projections.id()).
Johannes RudolphSeptember 28, 2005 at 9:23 AM
The last line should be
Subqueries.propertyIn("superBlub", detachedCrit ) ) );
Details
Assignee
UnassignedUnassignedReporter
Johannes RudolphJohannes RudolphLabels
Components
Priority
Minor
Details
Details
Assignee
Reporter
Johannes RudolphLabels
Components
Priority
Minor
If you use a subquery in a criteria query and there is no projection, the execution of the query will fail by throwing a NullPointerException:
Caused by: java.lang.NullPointerException
at
org.hibernate.loader.criteria.CriteriaQueryTranslator.getProjectedTypes(Crit
eriaQueryTranslator.java:298)
at
org.hibernate.criterion.SubqueryExpression.toSqlString(SubqueryExpression.ja
va:56)
at
org.hibernate.criterion.LogicalExpression.toSqlString(LogicalExpression.java
:39)
org.hibernate.loader.criteria.CriteriaQueryTranslator.getWhereCondition(Crit
eriaQueryTranslator.java:314)
...
I think it is expected behaviour that restrictions only work on 1-dimensional return values of subqueries so it would be nice if Hibernate would mention that somewhere.
It would be nice if you could just write:
Criteria crit = dbSession.createCriteria(Bla.class);
DetachedCriteria detachedCrit = DetachedCriteria.forClass(Blub.class).add( Restrictions.eq("condition", Boolean.FALSE));
crit.add( Restrictions.or( Restrictions.isNull("superBlub"),
Subqueries.in("superBlub", detachedCrit ) ) );
since Hibernate entities could be seen as "entities" so Hibernate should automatically transform it into:
DetachedCriteria detachedCrit = DetachedCriteria.forClass(Blub.class).add( Restrictions.eq("condition", Boolean.FALSE))
.setProjection( Projections.id() );
crit.add( Restrictions.or( Restrictions.isNull("superBlub"),
Subqueries.propertyIn("ueberPartner", detachedCrit ) ) );