I just took latest cvs hibernate3. I am using classic query - and the queries that used to work, doesn't work with this latest. It gives an error saying :
java.lang.UnsupportedOperationException: select clause aliases ar
e not supported by classic parser
at org.hibernate.hql.classic.QueryTranslatorImpl.getReturnAliases(QueryTranslatorImpl.java:230)
at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:95)
at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:52)
at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:71)
at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:108)
at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:88)

please, can this be fixed? I need to use the latest cvs due to some bugs that got fixed and I need to implement this newly build hibernate3.jar

That's probably just a missing "as" somewhere. Can you post your now-broken query?

actually, I do have "as" in all of my hql queries and none of them are working. e.g:
generated select is -
SELECT emp FROM com.company.Employees AS emp WHERE emp.valid = 1

That's almost SQL.. try the pure HQL version:

oops, I broke that I guess. post a jira bug if you like. or better yet, stop using the classic translator ;)

i seriously need to think about removing that thing soon...

thanks Steve. I will post a jira bug. Regarding not to use classic query, I have no choice, since I have several other queries that don't work with AST for some reason for sub select queries that involves sub-class properties. I will post jira for this one also. Can you see if this can be fixed for the AST query - Then, I can switch to that one.

I have no idea what you are talking about. Is there a specific JIRA issue referencing what you believe to be incorrect behavior in the AST translator?