Bug 981720
| Summary: | Upgrade to Hibernate 4.2.0.SP1 | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Dave Stahl <dstahl> |
| Component: | Hibernate | Assignee: | Dave Stahl <dstahl> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | Russell Dickenson <rdickens> |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | akovari, brmeyer, cdewolf, istudens, jdoyle, msimka, myarboro, rdickens, smarlow, tkirby, zroubali |
| Target Milestone: | ER3 | ||
| Target Release: | EAP 6.1.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
HHH-6813
https://hibernate.atlassian.net/browse/HHH-6813
Having an @Id @OneToOne (derived primary key from a foreign key) causes NullPointerExceptions during any query
-----------------------------------------------
(All of the following fixes compose a near
complete re-write of how Hibernate generates
names for unique, foreign, and index constraints
that are not explicitly named in mappings. The
set should be taken holistically, rather than
individually -- most iteratively build on each
other.)
HHH-1904 (superseded), HHH-8217, HHH-8269
https://hibernate.atlassian.net/browse/HHH-1904
https://hibernate.atlassian.net/browse/HHH-8217
https://hibernate.atlassian.net/browse/HHH-8269
To ensure a maximum identifier length, generate all non-named constraint names by hashing a concatenation of the table name and an alphabetical ordering of column names. HHH-8217 supersedes HHH-1904 with the correct approach.
HHH-8092, HHH-8162
https://hibernate.atlassian.net/browse/HHH-8092
https://hibernate.atlassian.net/browse/HHH-8162
The pre-existance of unique constraints cannot be easily/consistently checked within JDBC. Methods for foreign keys and indexes exist, but uniques would require very dialect-specific functions to be used. Instead, allow unique constraint handling during a schema update to be configurable: completely ignore uniques altogether or attempt to (re-)create the constraints and ignore any errors (but include a warning log).
HHH-8178
https://hibernate.atlassian.net/browse/HHH-8178
The internal processing of natural keys was corrected to ensure all of its columns were going into a single unique constraint. The hashed name changes, above, had broken it.
HHH-8275
https://hibernate.atlassian.net/browse/HHH-8275
Union-subclass inheritance mappings were incorrectly using the parent table name in the unique constraint "alter table" statement, instead of the sub-table.
HHH-8273
https://hibernate.atlassian.net/browse/HHH-8273
Corrected "unique-key" documentation to reflect all above changes.
-----------------------------------------------
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-16 20:23:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 979103 | ||
|
Description
Dave Stahl
2013-07-05 15:12:04 UTC
reassigned to Dave Stahl since he created the PR Verified on EAP 6.1.1.ER3 *** Bug 979098 has been marked as a duplicate of this bug. *** @Brett could you prepare text for release notes? This upgrade fixes several issues *** Bug 962421 has been marked as a duplicate of this bug. *** Rough draft docs for all fixes added. Russell, in light of the email discussion, was this route incorrect? It's a bit of an odd case due to processes getting jumbled up in this release. The bug fixes were closed and marked as duplicates of this component upgrade ticket (long story). |