HHH-18589 Properly handle temporals in BC era #10705
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| } | ||
| } | ||
|
|
||
| public static Instant toInstant(Timestamp timestamp) { |
Check notice
Code scanning / CodeQL
Confusing overloading of methods Note
|
This PR also addresses some issues with date conversion between java.time other APIs where the same epoch millisecond might mean different dates for various reasons. It's also worth to mention that the JDBC drivers sometimes rely on a certain epoch millisecond interpretation when passing temporal values, which needs to be accounted for. |
|
Thanks for your pull request! This pull request does not follow the contribution rules. Could you have a look? ❌ All commit messages should start with a JIRA issue key matching pattern › This message was automatically generated. |
1 participant
[Please describe here what your change is about]
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.
https://hibernate.atlassian.net/browse/HHH-18589