Menu
▾
▴
hibernate-issues
|
From: Steve E. (JIRA) <no...@at...> - 2005-12-13 13:36:54
|
HQL: order-by clause column list
--------------------------------
Key: HHH-1267
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267
Project: Hibernate3
Type: Improvement
Components: core
Reporter: Steve Ebersole
Assigned to: Steve Ebersole
Priority: Minor
Fix For: 3.1.1
HQL currently always results in using qualified column names in the order-by clause. Some databases (ok DB2) actually do not support this in all cases. And really according to the SQL spec, it is not the specified thing to do. Essentially the SQL spec says that if select-clause column aliases are used, those column aliases (or the column indexes) should be used in the order-by clause.
This should be the non-default behavior as it'll be more intensive of the query parser to achieve this.
--
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
|
|
From: Steve E. (JIRA) <no...@at...> - 2006-01-12 03:54:45
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267?page=all ] Steve Ebersole updated HHH-1267: -------------------------------- Fix Version: (was: 3.1.1) 3.1.2 > HQL: order-by clause column list > -------------------------------- > > Key: HHH-1267 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267 > Project: Hibernate3 > Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.1.2 > > > HQL currently always results in using qualified column names in the order-by clause. Some databases (ok DB2) actually do not support this in all cases. And really according to the SQL spec, it is not the specified thing to do. Essentially the SQL spec says that if select-clause column aliases are used, those column aliases (or the column indexes) should be used in the order-by clause. > This should be the non-default behavior as it'll be more intensive of the query parser to achieve this. -- 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 |
|
From: Steve E. (JIRA) <no...@at...> - 2006-01-27 23:48:47
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267?page=all ] Steve Ebersole updated HHH-1267: -------------------------------- Fix Version: (was: 3.1.2) 3.1.3 > HQL: order-by clause column list > -------------------------------- > > Key: HHH-1267 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267 > Project: Hibernate3 > Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.1.3 > > > HQL currently always results in using qualified column names in the order-by clause. Some databases (ok DB2) actually do not support this in all cases. And really according to the SQL spec, it is not the specified thing to do. Essentially the SQL spec says that if select-clause column aliases are used, those column aliases (or the column indexes) should be used in the order-by clause. > This should be the non-default behavior as it'll be more intensive of the query parser to achieve this. -- 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 |
|
From: Steve E. (JIRA) <no...@at...> - 2006-03-07 21:30:57
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267?page=all ] Steve Ebersole updated HHH-1267: -------------------------------- Fix Version: (was: 3.1.3) 3.2.0 > HQL: order-by clause column list > -------------------------------- > > Key: HHH-1267 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267 > Project: Hibernate3 > Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0 > > > HQL currently always results in using qualified column names in the order-by clause. Some databases (ok DB2) actually do not support this in all cases. And really according to the SQL spec, it is not the specified thing to do. Essentially the SQL spec says that if select-clause column aliases are used, those column aliases (or the column indexes) should be used in the order-by clause. > This should be the non-default behavior as it'll be more intensive of the query parser to achieve this. -- 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 |
|
From: Steve E. (JIRA) <no...@at...> - 2006-03-16 15:38:14
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267?page=all ] Steve Ebersole updated HHH-1267: -------------------------------- Fix Version: (was: 3.2.0.alpha2) 3.2.0 > HQL: order-by clause column list > -------------------------------- > > Key: HHH-1267 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267 > Project: Hibernate3 > Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0 > > > HQL currently always results in using qualified column names in the order-by clause. Some databases (ok DB2) actually do not support this in all cases. And really according to the SQL spec, it is not the specified thing to do. Essentially the SQL spec says that if select-clause column aliases are used, those column aliases (or the column indexes) should be used in the order-by clause. > This should be the non-default behavior as it'll be more intensive of the query parser to achieve this. -- 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 |
|
From: Antoine B. (JIRA) <no...@at...> - 2006-03-27 07:45:16
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267?page=comments#action_22602 ] Antoine Baudoux commented on HHH-1267: -------------------------------------- I have this problem with FrontBase. Do you have an idea of when this issue wil be resolved? This is very annoying, I cant do any sorting in HQL or in the criteria API. If you dont plan to solve this rapidly, can you tell me where to patch the code? Thanks! > HQL: order-by clause column list > -------------------------------- > > Key: HHH-1267 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267 > Project: Hibernate3 > Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0 > > > HQL currently always results in using qualified column names in the order-by clause. Some databases (ok DB2) actually do not support this in all cases. And really according to the SQL spec, it is not the specified thing to do. Essentially the SQL spec says that if select-clause column aliases are used, those column aliases (or the column indexes) should be used in the order-by clause. > This should be the non-default behavior as it'll be more intensive of the query parser to achieve this. -- 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 |
|
From: Steve E. (JIRA) <no...@at...> - 2006-03-27 17:36:39
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267?page=all ] Steve Ebersole updated HHH-1267: -------------------------------- Fix Version: (was: 3.2.0 cr1) 3.2.0 > HQL: order-by clause column list > -------------------------------- > > Key: HHH-1267 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267 > Project: Hibernate3 > Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0 > > > HQL currently always results in using qualified column names in the order-by clause. Some databases (ok DB2) actually do not support this in all cases. And really according to the SQL spec, it is not the specified thing to do. Essentially the SQL spec says that if select-clause column aliases are used, those column aliases (or the column indexes) should be used in the order-by clause. > This should be the non-default behavior as it'll be more intensive of the query parser to achieve this. -- 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 |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:50
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267?page=all ] Steve Ebersole updated HHH-1267: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > HQL: order-by clause column list > -------------------------------- > > Key: HHH-1267 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267 > Project: Hibernate3 > Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0 > > > HQL currently always results in using qualified column names in the order-by clause. Some databases (ok DB2) actually do not support this in all cases. And really according to the SQL spec, it is not the specified thing to do. Essentially the SQL spec says that if select-clause column aliases are used, those column aliases (or the column indexes) should be used in the order-by clause. > This should be the non-default behavior as it'll be more intensive of the query parser to achieve this. -- 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 |
|
From: Steve E. (JIRA) <no...@at...> - 2006-06-28 05:39:03
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267?page=all ] Steve Ebersole updated HHH-1267: -------------------------------- Component: query-hql (was: core) > HQL: order-by clause column list > -------------------------------- > > Key: HHH-1267 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267 > Project: Hibernate3 > Type: Improvement > Components: query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0 > > > HQL currently always results in using qualified column names in the order-by clause. Some databases (ok DB2) actually do not support this in all cases. And really according to the SQL spec, it is not the specified thing to do. Essentially the SQL spec says that if select-clause column aliases are used, those column aliases (or the column indexes) should be used in the order-by clause. > This should be the non-default behavior as it'll be more intensive of the query parser to achieve this. -- 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 |
|
From: Steve E. (JIRA) <no...@at...> - 2006-06-28 16:44:17
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267?page=all ] Steve Ebersole updated HHH-1267: -------------------------------- Fix Version: 3.2.1 (was: 3.2.0.cr3) > HQL: order-by clause column list > -------------------------------- > > Key: HHH-1267 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267 > Project: Hibernate3 > Type: Improvement > Components: query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.1 > > > HQL currently always results in using qualified column names in the order-by clause. Some databases (ok DB2) actually do not support this in all cases. And really according to the SQL spec, it is not the specified thing to do. Essentially the SQL spec says that if select-clause column aliases are used, those column aliases (or the column indexes) should be used in the order-by clause. > This should be the non-default behavior as it'll be more intensive of the query parser to achieve this. -- 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 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X