Bug 951563 - Hibernate envers @ElementCollection Map support failing -- nullable KEY
Summary: Hibernate envers @ElementCollection Map support failing -- nullable KEY
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Hibernate
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER1
: EAP 6.2.0
Assignee: Brett Meyer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: eap62-upgrade-hibernate425
TreeView+ depends on / blocked
 
Reported: 2013-04-12 13:38 UTC by Zbyněk Roubalík
Modified: 2015-09-01 04:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
HHH-8072 https://hibernate.atlassian.net/browse/HHH-8072 Envers' support of Map @ElementCollections was failing on certain dialects (namely, Sybase) due to its map table allowing PK columns to be nullable.
Clone Of:
Environment:
Last Closed: 2013-12-15 16:49:00 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Zbyněk Roubalík 2013-04-12 13:38:11 UTC 
We have severals evers test failures on db2-97, db2-10 and sybase157, due to a nullable key.

It is this [1] issue, which should be fixed in Hibernate 4.2.0.Final, but it seems like it is not.

[1] https://hibernate.atlassian.net/browse/HHH-8072

Jenkins job:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Hibernate/job/eap-60-hibernate-envers-testsuite/22/database=sybase157,jdk=java17_default,label=hibernate/
Comment 1 Brett Meyer 2013-04-15 20:06:28 UTC 
http://git.app.eng.bos.redhat.com/?p=hibernate/hibernate-core.git;a=shortlog;h=refs/heads/eap61-cp

It looks like this was committed after Strong tagged 4.2.0.Final in EAP git.  There were a few commits that were missed in the confusion between EAP ER builds.  Marking this as fixed in EAP 6.2.
Comment 2 Brett Meyer 2013-04-25 21:04:52 UTC 
Pushed to eap61-cp-updates and will be merged into Hibernate's future EAP 6.2 branch.
Comment 3 Martin Simka 2013-11-20 09:07:53 UTC 
verified on EAP 6.2.0.CR2
Note You need to log in before you can comment on or make changes to this bug.