[hibernate-issues] [JIRA] (HHH-14009) LockModeType.OPTIMISTIC_FORCE_INCREMENT causes Hibernate to issue a second update statement when an entity is already marked as dirty

[Martin T. (JIRA)]

Martin T. ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5eb68b676c84140b9e9c3625 ) *updated* an issue

Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiODFmNjkyZWY4Y2QyNGQ1ZjhmYTkxOGVlMTQxNTU2MTMiLCJwIjoiaiJ9 ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14009?atlOrigin=eyJpIjoiODFmNjkyZWY4Y2QyNGQ1ZjhmYTkxOGVlMTQxNTU2MTMiLCJwIjoiaiJ9 ) HHH-14009 ( https://hibernate.atlassian.net/browse/HHH-14009?atlOrigin=eyJpIjoiODFmNjkyZWY4Y2QyNGQ1ZjhmYTkxOGVlMTQxNTU2MTMiLCJwIjoiaiJ9 ) LockModeType.OPTIMISTIC_FORCE_INCREMENT causes Hibernate to issue a second update statement when an entity is already marked as dirty ( https://hibernate.atlassian.net/browse/HHH-14009?atlOrigin=eyJpIjoiODFmNjkyZWY4Y2QyNGQ1ZjhmYTkxOGVlMTQxNTU2MTMiLCJwIjoiaiJ9 )

Change By: Martin T. ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5eb68b676c84140b9e9c3625 ) Affects versions: 5.4-backlog

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

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#100130- sha1:9665ecd )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hibernate-issues/attachments/20200624/954f70f0/attachment.html