Madeleine Andersson (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%...
) *created* an issue
Hibernate ORM (
https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNDBjYmU0Nzdm...
) / Bug (
https://hibernate.atlassian.net/browse/HHH-17051?atlOrigin=eyJpIjoiNDBjYm...
) HHH-17051 (
https://hibernate.atlassian.net/browse/HHH-17051?atlOrigin=eyJpIjoiNDBjYm...
) Default behavior for datatype Instant with a Oracle database does not behave as
expected. (
https://hibernate.atlassian.net/browse/HHH-17051?atlOrigin=eyJpIjoiNDBjYm...
)
Issue Type: Bug Affects Versions: 6.2.7 Assignee: Unassigned Created: 08/Aug/2023 22:16 PM
Environment: Oracle database v. 19.x Priority: Major Reporter: Madeleine Andersson (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%...
)
We have Oracle as database, version 19.x set in Timezone GMT+2 We are running hibernate
with TimeZone Europe/Stockholm set. Column holding Instant is TIMESTAMP.
Saving and Getting dateValues does not work as expected.
If you save an entity with the time: 2023-08-09T03:08:11.063446900Z
And then try to get entities within a period of time:
2023-08-09T02:08:11.063446900Z - 2023-08-09T04:08:11.063446900Z
No entities are found.
If you set the "hibernate.type.preferred_instant_jdbc_type" to TIMESTAMP, then
test will run OK. If you keep it to default, that is TIMESTAMP_UTC, test will fail, no
entity will be found.
Link to testcase: Test Case (
https://github.com/madeleine-a/hibernate-test-case-templates
)
(
https://hibernate.atlassian.net/browse/HHH-17051#add-comment?atlOrigin=ey...
) Add Comment (
https://hibernate.atlassian.net/browse/HHH-17051#add-comment?atlOrigin=ey...
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira....
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em...
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100234- sha1:9e2db29 )