Unexpected AST node error - Migrate from 2.1 to 3.05

dshen · **Joined:** Thu May 26, 2005 6:31 pm **Posts:** 19

Hibernate version: 3.05

HQL: select techProfile from TechProfile techProfile left outer join techProfile.deal.ses ses where ses.id = :seId and techProfile.status != 'closed' order by techProfile.deal.name and techProfile.targetCompletionDate

Full stack trace of any exception that occurs: Caused by: <AST>:0:0: unexpected AST node: and at org.hibernate.hql.antlr.HqlSqlBaseWalker.expr(HqlSqlBaseWalker.java:958) at org.hibernate.hql.antlr.HqlSqlBaseWalker.orderExprs(HqlSqlBaseWalker.java:1190) at org.hibernate.hql.antlr.HqlSqlBaseWalker.orderClause(HqlSqlBaseWalker.java:1166) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:449) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:201) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:151) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:189) ... 26 more

The same code (HQL) is working under hibernate2. Is there any update with HQL interpreter in Hibernate3?

Did some search. Someone had the similar proble and he claimed that the new HQL does not support nexted bean property, which I don't think is the case. Please help.

pksiv · **Posted:** Wed Oct 19, 2005 2:48 pm

dshen wrote:

Hibernate version: 3.05

...
....
The same code (HQL) is working under hibernate2. Is there any update with HQL interpreter in Hibernate3?

Did some search. Someone had the similar proble and he claimed that the new HQL does not support nexted bean property, which I don't think is the case. Please help.

You should read, very carefully, the H3 Migration Guide. http://www.hibernate.org/250.html

There is a completely new HQL Query Translator in H3. You can use the old one by adding

Code:

<property name="query.factory_class">org.hibernate.hql.classic.ClassicQueryTranslatorFactory</property>

to your hibernate.cfg.xml but that should only be done as a last resort since there are some new features that you won't be able to use with it.

dshen · **Joined:** Thu May 26, 2005 6:31 pm **Posts:** 19

Thanks. Like you said

Quote:

that should only be done as a last resort since there are some new features that you won't be able to use with it.

All my unit test passed, besides two - this one and a null pointer exception one. Do not want to go to that rout yet.

pksiv · **Posted:** Wed Oct 19, 2005 2:58 pm

dshen wrote:

Hibernate version: 3.05

HQL: select techProfile from TechProfile techProfile left outer join techProfile.deal.ses ses where ses.id = :seId and techProfile.status != 'closed' order by techProfile.deal.name and techProfile.targetCompletionDate

Looking more closely at your query and the error message, try changing the ORDER BY statement to

Code:

order by techProfile.deal.name, techProfile.targetCompletionDate

dshen · **Joined:** Thu May 26, 2005 6:31 pm **Posts:** 19

It got fixed. Thanks!