-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: EAP 5.0.0.CR1, EAP 5.0.0.BETA, EAP 5.0.0, EAP 5.0.1.CR1
-
Fix Version/s: EAP_EWP 5.1.0
-
Component/s: Hibernate
-
Labels:None
-
Environment:
JDK 1.6
-
Affects:Release Notes
HashMaps and HashSets iteration order in JDK 1.6 differs from what it was in JDK 1.4 and 1.5 and it is causing the order of columns in union clauses or union-subclasses to change, which can have a large impact on performance.
The change in column order is consistent across subclasses, so the change in the resulting queries do not cause a failure. This is really a performance issue.
The column order should be the same as is mapped in the entity class. It is clear from the code that this is what was intended.
See http://opensource.atlassian.com/projects/hibernate/browse/HHH-3338 for more details.
IMO, If there isn't enough time to fix this, it should be noted in the release notes as a "known" issue.
- relates to
-
-
- Resolved
-
