HQL Parsing improvements ------------------------ Key: HHH-4628 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4628 Project: Hibernate Core Issue Type: Improvement Components: query-hql Affects Versions: 3.2.2 Environment: Hibernate 3.22 Ga, Oracle 10g Reporter: Frank Daspro Attachments: sql1.txt, sql2.txt The same HQL is being parsed/mangled differently on different servers and possibly differently after server restarts. This is causing our Oracle Optimizer to intermittently optimise the SQL differently and requiring manual intervention by our DBAs to re-optimise these queries. I am informed by a Hibernate technical consultant that there is element of randomness in the mangled column name generation. An example of the HQL parsing inconsistencies are attached. Both outputs are from the identical HQL and producing different mangled column names. It would be much appreciated if this parsing could be modified to use a deterministic algorithm in producing mangled column names. -- 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