Skip to:

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

Redesign follow-on locking

Description

When an application asks Hibernate to perform a query and apply pessimistic locks at the database level, there are various cases where we are not able to accomplish that with a single query. Hibernate has a feature called “follow-on locking” which attempts to allow for this. However, there are a number of improvements we should consider here (per sub tasks).

In general, this breaks down into -

  1. Minimize when we need follow-on locking

  2. Improve how we do follow-on locking

0% Done
Type
Key
Summary
Priority
Story Points
Assignee
Status

Activity

Show:
Steve Ebersole
updated the Descriptionlast week
When an application asks Hibernate to perform a query and apply pessimistic locks at the database level, there are various cases where we are not able to accomplish that with a single query. Hibernate has a feature called “follow-on locking” which attempts to allow for this. However, there are a number of improvements we should consider here (per sub tasks).
When an application asks Hibernate to perform a query and apply pessimistic locks at the database level, there are various cases where we are not able to accomplish that with a single query. Hibernate has a feature called “follow-on locking” which attempts to allow for this. However, there are a number of improvements we should consider here (per sub tasks). In general, this breaks down into - # Minimize when we need follow-on locking # Improve how we do follow-on locking
Steve Ebersole
created the Issuelast week

Details

Assignee

Reporter

Priority

Created last week
Updated last week

Flag notifications