[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-892) HQL parser does not resolve alias in ORDER BY clause
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-892?page=co...
]
salvin francis commented on HHH-892:
------------------------------------
I wonder why the usage of "col_0_0_" is considered 'normal' and not a
hack
I feel that providing such solutions is not correct to any client.
I am using the CASE ...WHEN...END functionality in my system
My situation is that i am retrieving some values from a table in the form
"Critical","High","Medium","Low"
in my case an Alphabetical sort would of couse screw it.
and there is No way my client would allow me to add an extra column in his DB
I would obviously deter from using a SQL query here as it would change my complete system
approach already implemented in
HQL parser does not resolve alias in ORDER BY clause
-----------------------------------------------------
Key: HHH-892
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-892
Project: Hibernate Core
Issue Type: Bug
Components: query-hql
Affects 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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira