Hi !

Isn't it possible, to have parameters in subqueries ?
Here's may query and the excepetion thrown by hibernate:

queryString =
"select qst.id "
+ "from questions.DBAssessQuestion as qst "
+ "where qst.metaData.values in elements ( "
+ " from metadata.IntegerDimValue as dimVal "
+ " where dimVal.dimension = :dimension "
+ " and dimVal.intValue = :intValue "
+ ")";

Query query = session.createQuery(queryString);
query.setEntity("dimension", intVal.getDimension());
query.setEntity("intValue", intVal.getIntValue());

The subquery (from metadate ... :intValue) runs without problem if used standalone. But this question throws the following exception:

net.sf.hibernate.QueryException: Named parameter does not appear in Query: dimension [select qst.id from questions.DBAssessQuestion as qst where qst.metaData.values in elements ( from metadata.IntegerDimValue as dimVal where dimVal.dimension = :lDim and dimVal.intValue = :intValue )]

...or is it just a odd error-message and the problem is somewhere else in the question?

Thanks for any hint !

P.S.: I'm using hibernate 2.1.2

values is a collection? Then it should be something like:

Thank you for your quick response:

Yes ! values is a collection (more precisely: a java.util.List).

I changed now the query as you suggested it:




Unfortunatly, the exception remains the same:

Check your code. The exception message tells you quite clearly that the parameter is really named :lDim.

Hi !

...and sorry for the confusion:
The error-message in my first positing had a copy&paste error. (I tried several parameter-names since there were some postings in this forum, saying that the hql-parser in older hibernate version had problems with some parameter-names.)

In fact: Hibernate really complains about the paramter "dimension" (and not "lDim")

So here is the original exception-text:

Submit a simple test case to JIRA. May be a bug with the new named-parameter-validation stuff.

Max, is that a possibility?

...one week later. :-(

I finally got the time to set up a simple test case. I submitted it now to JIRA as you suggested. The report-number is HB-915.

The correct, working query is:




The elements() construct applies to collections, not subqueries.

Sorry about the confusing exception message.

An alternative, equivalent formulation of this query is:




And a much, much better formulation is:



I don't know why you had this unnecessary subselect.