Skip to content

GH-3885: Change LockRepository to LocalDateTime #3886

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
Sep 12, 2022

Conversation

artembilan
Copy link
Member

Fixed #3885

Turns out the Date is stored into DB without time zone, so instances in different zones may not react properly for updates

  • Change the logic in the DefaultLockRepository to store time via LocalDateTime.now(ZoneOffset.UTC) to ensure that all instance deals with the same time representation without time zone offsets

Fixed spring-projects#3885

Turns out the `Date` is stored into DB without time zone, so instances
in different zones may not react properly for updates

* Change the logic in the `DefaultLockRepository` to store time via
`LocalDateTime.now(ZoneOffset.UTC)` to ensure that all instance deals with the same
time representation without time zone offsets
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.

Default JDBC lock repository does not use time zone when storing creation date, causing "lock"
2 participants