Skip to content

GH-3866: DefLockRepository: expose query setters #8606

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 1, 2023

Conversation

artembilan
Copy link
Member

Fixes #3866

Some RDBMS vendors (or their JDBC drivers) may just log the problem without throwing an exception.

  • Expose setters for UPDATE and INSERTS queries in the DefaultLockRepository to let end-user to modify them respectively, e.g. be able to add a PostgreSQL ON CONFLICT DO NOTHING hint.
  • Refactor DefaultLockRepository to Instant instead of LocalDateTime with zone offset.
  • Refactor ttl property to Duration type
  • Fix dead-lock typo to deadlock

Fixes spring-projects#3866

Some RDBMS vendors (or their JDBC drivers) may just log the problem
without throwing an exception.

* Expose setters for UPDATE and INSERTS queries in the `DefaultLockRepository`
to let end-user to modify them respectively, e.g. be able to add a PostgreSQL
`ON CONFLICT DO NOTHING` hint.
* Refactor `DefaultLockRepository` to `Instant` instead of `LocalDateTime`
with zone offset.
* Refactor `ttl` property to `Duration` type
* Fix `dead-lock` typo to `deadlock`
@artembilan artembilan requested a review from garyrussell May 1, 2023 20:38
@garyrussell garyrussell merged commit 90bc65e into spring-projects:main May 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

duplicate key value violates unique constraint "int_lock_pk"
2 participants