Skip to:

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

Cascading inserts are failing after upgrade

Description

Cascading inserts are failing in 4.1.12 .
Looks like it is because of https://hibernate.atlassian.net/browse/HHH-5732
Testcase attached.
There is an extra SQL generated in 4.1.12 when compared to 4.1.10
Hibernate: update orders set OrderID=? where OrderID=?

Attachments

2
  • 18 Aug 2014, 12:24 PM
  • 11 Aug 2014, 06:19 AM

Activity

Show:

Brett Meyer April 22, 2015 at 9:14 PM

Closing rejected issues.

Himavanth Rachamsetty November 19, 2014 at 6:56 AM

I am not using an ordercolumn here.
I am using map and map-key as opposed to list and ordercolumn.
Please check again and re-open this bug.

Himavanth Rachamsetty November 5, 2014 at 10:00 AM

There can be scenario where a map needs to be used to store the OrderID as key and the Order entity as value.

And this was working absolutely fine in 4.1.10.
Why would you break backward compatibility.

Former user August 18, 2014 at 7:28 PM

@OrderColumn should be used with a List, not a Map.

Former user August 18, 2014 at 7:03 PM

What version did you upgrade from?

Rejected

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

Created August 11, 2014 at 6:19 AM
Updated April 22, 2015 at 9:14 PM
Resolved August 18, 2014 at 7:28 PM

Flag notifications