We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As of now, LocalDate is converted into milliseconds with the system default timezone: JavaDateColumnType.kt
This does not work in our use case where:
With system default timezone there is no guarantee that the day will be the same on different devices.
Using UTC for the millisecond conversion would solve this problem, but changing the current behaviour might break existing installations.
What would be the best way to add the option to use UTC? If it can be a general solution I'll put it into a pull request of course.
Thank you for your help.
The text was updated successfully, but these errors were encountered:
The change to use UTC instead ZoneId.systemDefault() will be great.
ZoneId.systemDefault()
Sorry, something went wrong.
exposed-java-time
Successfully merging a pull request may close this issue.
As of now, LocalDate is converted into milliseconds with the system default timezone: JavaDateColumnType.kt
This does not work in our use case where:
With system default timezone there is no guarantee that the day will be the same on different devices.
Using UTC for the millisecond conversion would solve this problem, but changing the current behaviour might break existing installations.
What would be the best way to add the option to use UTC? If it can be a general solution I'll put it into a pull request of course.
Thank you for your help.
The text was updated successfully, but these errors were encountered: