[hibernate-issues] [JIRA] (HHH-14043) Two concurrent element shifts in a list damage database integrity.

[Björn Zurmaar (JIRA)]

Björn Zurmaar ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ecd86c3dacd410c1f8c8da5 ) *commented* on HHH-14043 ( https://hibernate.atlassian.net/browse/HHH-14043?atlOrigin=eyJpIjoiMjAxYmY3ODMwNzkxNDk3Mjk0MTMxMzQxOTM4OWNjMmMiLCJwIjoiaiJ9 )

Re: Two concurrent element shifts in a list damage database integrity. ( https://hibernate.atlassian.net/browse/HHH-14043?atlOrigin=eyJpIjoiMjAxYmY3ODMwNzkxNDk3Mjk0MTMxMzQxOTM4OWNjMmMiLCJwIjoiaiJ9 )

The relevant declaration is:

	@OneToMany(cascade=CascadeType.ALL,fetch=FetchType.EAGER)
	@JoinColumn(referencedColumnName= "id" ,name= "foo_id" )
	@OrderColumn
	List<Bar> bars;

So this should be a unidirectional parent-owning-side-child association mapping. While the article is pretty interesting stuff I don’t see how this helps with the problem. The problem is not locking from my point of view.

( https://hibernate.atlassian.net/browse/HHH-14043#add-comment?atlOrigin=eyJpIjoiMjAxYmY3ODMwNzkxNDk3Mjk0MTMxMzQxOTM4OWNjMmMiLCJwIjoiaiJ9 ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14043#add-comment?atlOrigin=eyJpIjoiMjAxYmY3ODMwNzkxNDk3Mjk0MTMxMzQxOTM4OWNjMmMiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100129- sha1:b514962 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hibernate-issues/attachments/20200618/7fea0947/attachment.html