When migrating an application from Hibernate2 to Hibernate3, I was hit by the following diagnostic:

Caused by: line 1:99: unexpected char: '#'
at org.hibernate.hql.antlr.HqlBaseLexer.nextToken(HqlBaseLexer.java:278)
at antlr.TokenBuffer.fill(TokenBuffer.java:69)
at antlr.TokenBuffer.LA(TokenBuffer.java:80)
at antlr.LLkParser.LA(LLkParser.java:52)
at org.hibernate.hql.antlr.HqlBaseParser.identPrimary(HqlBaseParser.java:3297)
at org.hibernate.hql.antlr.HqlBaseParser.primaryExpression(HqlBaseParser.java:2906)
at org.hibernate.hql.antlr.HqlBaseParser.atom(HqlBaseParser.java:2784)
at org.hibernate.hql.antlr.HqlBaseParser.unaryExpression(HqlBaseParser.java:2665)
at org.hibernate.hql.antlr.HqlBaseParser.multiplyExpression(HqlBaseParser.java:2691)
at org.hibernate.hql.antlr.HqlBaseParser.additiveExpression(HqlBaseParser.java:532)
at org.hibernate.hql.antlr.HqlBaseParser.relationalExpression(HqlBaseParser.java:2112)
at org.hibernate.hql.antlr.HqlBaseParser.equalityExpression(HqlBaseParser.java:1975)
at org.hibernate.hql.antlr.HqlBaseParser.negatedExpression(HqlBaseParser.java:1938)


The query causing is
from EnumPatternLevel epl where epl.serialNo=:serialNo order by serial#, run_code, applicability_date, enum_group, ord

The problem is in the # sign in serial#.


Complaining about the # is new behaviour in Hibernate 3, but anyway I was always confused about the fact that the order by clause had to reference the actual column names and not the names of the attributes mapped to those columns (In the actual case the attribute serialNo is mapped to the column serial#).

As this is used with a 3rd party database I have no possibility of renaming the column.

- Erik

???

Maybe this part of my posting was too short to convey my question.

Anyway, I'll try again: The query in my original posting referenced an attribute in my Java object called serialNo that is mapped to the database column serial#. What has puzzled me in both Hibernate 2 and 3 is that when adding an 'order by' clause containing this attribute to the query, I have to refer to it via its column name and not via its mapped attribute name.

- Erik

Of course you have to use the name of the property, not the column name.

Yes, that's how I think it should be, but if I change the query in my original posting to

return session.createQuery("from EnumPatternLevel epl where epl.serialNo=:serialNo order by serialNo, runCode, applicabilityDate, enumGroup, ord").
setInteger("serialNo", serialNo).
list();

i.e. by using the property names in the order by clause, I get:

Caused by: com.sybase.jdbc2.jdbc.SybSQLException: Invalid column name 'serialNo'.

at com.sybase.jdbc2.tds.Tds.processEed(Tds.java:2884)
at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:2206)
at com.sybase.jdbc2.jdbc.ResultGetter.nextResult(ResultGetter.java:69)
at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:220)
at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:203)
at com.sybase.jdbc2.jdbc.SybStatement.queryLoop(SybStatement.java:1596)
at com.sybase.jdbc2.jdbc.SybStatement.executeQuery(SybStatement.java:1581)
at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeQuery(SybPreparedStatement.java:96)
at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:71)
at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:107)
at org.hibernate.loader.Loader.getResultSet(Loader.java:1183)
at org.hibernate.loader.Loader.doQuery(Loader.java:363)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:203)
at org.hibernate.loader.Loader.doList(Loader.java:1499)
... 93 more


In Hibernate 2 I had to use the column names, but there the # in serial# was accepted.

Are we still discussing whether this is pilot error or are we getting close to submitting a bug report ?

- Erik

You have to use order by epl.serialNo

Genau -- so isst es. Vielen Dank, Michael.

- Erik

Kein Problem :)