Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Parent entity gets an extra revision when child is updated

Description

I'm experiencing a different behavior with Hibernate ORM 4.3.11 with extra revisions being created for parent entities when a child (@OneToOne) is modified.
With Hibernate 4.3.10 it's working as expected:

  1. the parent and child objects are created (one INSERT each, one revision each)

  2. the child object is updated (one UPDATE for the child, one revision)
    With Hibernate 4.3.11, step 2 triggers an extra revision for the parent (but no update since it has not changed).

I simplified the model as much as I could in the attached test case.

If I remove the (unused) discrepancyList, the test passes.
If issueDate is left as null during the initial insert, the test passes.
If the TemporalType is changed to TIMESTAMP (but not TIME), the test passes.

Attachments

2

Activity

Show:

Chris CranfordJanuary 3, 2016 at 11:45 PM

, I cannot reproduce this behavior under ORM5 after porting your test case to an Envers test case. Please see my PR I am attaching to this issue and let me know whether or not I need to make any adjustments. The test case results in a single revision being created which mimics the behavior you described from 4.3.10.

Steve EbersoleOctober 28, 2015 at 3:25 AM

As part of verifying that this issue affects 5.0, please just set the "Affects version". Leave the "verify-affects-5.0" label and leave the issue in "Awaiting Response" status; these are critical for us to be able to track these verifications and triage them. Thanks.

Steve EbersoleOctober 27, 2015 at 7:16 PM

This bug report does not indicate that the reported issue affects version 5.x. Versions prior to 5.x are no longer maintained. It would be a great help to the Hibernate team and community for someone to verify that the reported issue still affects version 5.x. If so, please add the 5.x version that you verified with to the list of affected-versions and attach the (preferably SSCCE) test case you used to do the verification to the report; from there the issues will be looked at during our triage meetings.

For details, see http://in.relation.to/2015/10/27/great-jira-cleanup-2015/

Olivier SambourgOctober 21, 2015 at 1:09 PM
Edited

Sorry it seems the test case I uploaded does not work either with Hibernate 4.3.10, I must have "simplified" the original test too much. I'll upload a new one ASAP.

Edit: done, new test class passes with 4.3.10 and not with 4.3.11

Out of Date

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

Created October 21, 2015 at 11:27 AM
Updated August 11, 2016 at 5:47 PM
Resolved August 11, 2016 at 5:47 PM