Skip to content

HHH-18589 Properly handle temporals in BC era #10705

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

beikov
Copy link
Member

@beikov beikov commented Aug 7, 2025

[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

}
}

public static Instant toInstant(Timestamp timestamp) {

Check notice

Code scanning / CodeQL

Confusing overloading of methods Note

Method DateTimeUtils.toInstant(..) could be confused with overloaded method
toInstant
, since dispatch depends on static types.
@beikov
Copy link
Member Author

beikov commented Aug 11, 2025

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.
I assume that this is the reason for failures in Quarkus: quarkusio/quarkus#37720

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.

1 participant