Hibernate version: 2.1.4

Mapping documents:
<!-- Parent Class -->
<many-to-one
name="child"
class="Child"
not-null="true"
>
<column name="CHILD_ID" />
</many-to-one>

<!-- Child class -->
<property
name="number"
type="java.lang.Integer"
column="NUMBER"
length="9"
/>

Full stack trace of any exception that occurs:

could not resolve property: x.number of: Parent


Name and version of the database you are using: Oracle 9.1.2

Code:

Criteria query = session.createCriteria(Parent.class);
query.createAlias("child", "x");
query.addOrder(Order.desc("x.number"));
query.setFetchMode("child",FetchMode.EAGER);


I've read about doing this kind of ordering on a Criteria query as being part of 2.1.2+ and I'm using 2.1.4. Is it possible in 2.1.4 and if so am I doing this correctly?

Hi,

I am running into the same problem!

Does anyone knows if this feture works?

Thanks a lot!
Michael.

Looking through code it seems that it cannot be done.
Or maybe I'm mistaken?

Rgds, Ales

-----------------------------------

Used in Order.toSqlString on AbstractCriterion with EMPTY_MAP

protected static String[] getColumns(SessionFactoryImplementor sessionFactory, Class persistentClass, String property, String alias, Map aliasClasses) throws HibernateException {
if ( property.indexOf('.')>0 ) {
String root = StringHelper.root(property);
Class clazz = (Class) aliasClasses.get(root);
//since alliasClasses map is empty this is null
if (clazz!=null) {
persistentClass = clazz;
alias = root;
property = property.substring( root.length()+1 );
}
}
return getPropertyMapping(persistentClass, sessionFactory).toColumns(alias, property);
}

AbstractPropertyMapping doesn't hold nested properties (ok, association identifiers excluded), so both columns and template are null --> QueryException.

public String[] toColumns(String alias, String propertyName)
throws QueryException {

String[] columns = (String[]) columnsByPropertyPath.get(propertyName);
if (columns==null) {
String template = (String) formulaTemplatesByPropertyPath.get(propertyName);
if (template==null) {
throw new QueryException( "could not resolve property: " + propertyName + " of: " + getClassName() );
}
else {
return new String[] { StringHelper.replace(template, Template.TEMPLATE, alias) };
}
}
else {
return StringHelper.qualify(alias, columns);
}
}

Use latest release of HB3

Does this code do the trick?

No. You should get this exception.

Subcriteria:

public Criteria addOrder(Order order) {
throw new UnsupportedOperationException("subcriteria cannot be ordered");
}

I can attest that this fully works under Hib 3 Beta 3. It's been an annoyance for us in the past so when I saw that it might work now I decided to give it a go.

The new Criteria features are a nice surprise, I didn't expect any enhancements until 3.1