[hibernate-issues] [JIRA] (HHH-16056) Pessimistic write lock does not always return latest database state

pioneer.vvs(a)gmail.com ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a96c11... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzk4OGMxMTYw... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16056?atlOrigin=eyJpIjoiYzk4OG... ) HHH-16056 ( https://hibernate.atlassian.net/browse/HHH-16056?atlOrigin=eyJpIjoiYzk4OG... ) Pessimistic write lock does not always return latest database state ( https://hibernate.atlassian.net/browse/HHH-16056?atlOrigin=eyJpIjoiYzk4OG... ) Issue Type: Bug Affects Versions: 5.6.14 Assignee: Unassigned Created: 17/Jan/2023 10:11 AM Priority: Major Reporter: pioneer.vvs(a)gmail.com ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a96c11... ) Like https://hibernate.atlassian.net/browse/HHH-12222 ( https://hibernate.atlassian.net/browse/HHH-12222 ) It is cool recomendation to use optimistic lock, but what if need pessimistic? What to do if refresh clear locks? https://hibernate.atlassian.net/browse/HHH-16055 ( https://hibernate.atlassian.net/browse/HHH-16055 ) P/S Fresh data received from database, but use old that not actually. Give one example where it need(after lock use not actual data)? ( https://hibernate.atlassian.net/browse/HHH-16056#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16056#add-comment?atlOrigin=ey... ) 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.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:771690a )