From: Jere K. (JIRA) <no...@at...> - 2005-08-29 19:38:57
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-892?page=comments#action_19636 ] Jere Krischel commented on HHH-892: ----------------------------------- when you use the workaround, will it work the same in all environments? I'm worried that my "order by LASTNAME2_" will break on a different hibernate.cfg.xml file. Will Hibernate always generate the same SQL aliases, or will that be dialect dependent? works: .createQuery("from "+voType+" where upper(lastName) like upper(:startsWith) and role in (:roles) order by LASTNAME2_ asc") doesn't work: .createQuery("from "+voType+" where upper(lastName) like upper(:startsWith) and role in (:roles) order by lastName asc") generated sql: Hibernate: select adminuserv0_.ID as ID, adminuserv0_.LOGIN as LOGIN2_, adminuserv0_.LASTNAME as LASTNAME2_, adminuserv0_.FIRSTNAME as FIRSTNAME2_, adminuserv0_.MIDDLENAME as MIDDLENAME2_, adminuserv0_.EMAIL as EMAIL2_, adminuserv0_.STATUS as STATUS2_, adminuserv0_.PASSEXPIRATION as PASSEXPI8_2_, adminuserv0_.FAILEDATTEMPTS as FAILEDAT9_2_, adminuserv0_.CURRENTPASSWORD as CURRENT10_2_, adminuserv0_.CURRENTPWDSALT as CURRENT11_2_, adminuserv0_.CREATEDATE as CREATEDATE2_, adminuserv0_.CREATEDBY as CREATEDBY2_, adminuserv0_.PWDCHANGEDATE as PWDCHAN14_2_, adminuserv0_.PWDCHANGEDBY as PWDCHAN15_2_, adminuserv0_.ACCEPTEDTACDATE as ACCEPTE16_2_, adminuserv0_.PASSWORD as PASSWORD2_, adminuserv0_.ROLE as ROLE2_, adminuserv0_.JSESSIONID as JSESSIONID2_ from SBB.BROKER_ADMIN adminuserv0_ where (upper(adminuserv0_.LASTNAME)like upper(?)) and (adminuserv0_.ROLE in (? , ?)) order by LASTNAME2_ asc > HQL parser does not resolve alias in ORDER BY clause > ----------------------------------------------------- > > Key: HHH-892 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-892 > Project: Hibernate3 > Type: New Feature > Versions: 3.0.5 > Environment: Hibernate 3.0.5, MySQL, Tomcat > Reporter: Guido Laures > Priority: Minor > > > When using an alias for an ORDER BY clause this is not always correctly resolved. Example: > SELECT SUM(A.x) AS mySum FROM MyClass AS A GROUP BY A.y ORDER BY mySum > does not work because "mySum" is not resolved in the ORDER BY clause which results in an exception telling that mySum is an unknown column. > Workaround (not to say "hack") is using: > SELECT SUM(A.x) AS mySum FROM MyClass AS A GROUP BY A.y ORDER BY col_0_0_ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |