August 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16577) Index Out of Bound Exception

by Michael Kroll (JIRA)

Michael Kroll ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62ea4af... ) *commented* on HHH-16577 ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiZDI5NT... ) Re: Index Out of Bound Exception ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiZDI5NT... ) This seems to happen in combination with {code:java} @DynamicUpdate @OptimisticLocking(type = OptimisticLockType.DIRTY) {code} This i found by debugging: In our case {{ writtenFieldNames }} and writtenValues only contains the changed field and its new data as single entries, but the changed field is found in the attributeMapping on a bigger index. Then, this bigger index is used to access writtenValues. The misconception in this code here is that {{ writtenFieldNames }}, writtenValues and the attributeMapping are of the same size and order, which they are not. I am not sure why this goes away when disabling dynamic update and optimistic locking. ( https://hibernate.atlassian.net/browse/HHH-16577#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16577#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100234- sha1:9e2db29 )

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-17051) Default behavior for datatype Instant with a Oracle database does not behave as expected.

by Madeleine Andersson (JIRA)

Madeleine Andersson ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *commented* on HHH-17051 ( https://hibernate.atlassian.net/browse/HHH-17051?atlOrigin=eyJpIjoiOGIwNz... ) Re: Default behavior for datatype Instant with a Oracle database does not behave as expected. ( https://hibernate.atlassian.net/browse/HHH-17051?atlOrigin=eyJpIjoiOGIwNz... ) Have read the migration guide, and kind of read this “if possible, and falls back to timestamp " = will work. This config-change, will it work in the long run (incubating)? I can understand the asking for trouble, problem here is our database is already there, and it worked in hibernate 5.x So what do you suggest we should do in this case, to be future proof? Change database? Change datatype in entity? use the config: hibernate.type.preferred_instant_jdbc_type ( 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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100234- sha1:9e2db29 )

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-16945) CTE query cycle attribute evaluated incorrectly on MSSQL using collation "Latin1_General_CI_AS"

by Christian Beikov (JIRA)

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-17051) Default behavior for datatype Instant with a Oracle database does not behave as expected.

by Christian Beikov (JIRA)

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-17051) Default behavior for datatype Instant with a Oracle database does not behave as expected.

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-17051 ( https://hibernate.atlassian.net/browse/HHH-17051?atlOrigin=eyJpIjoiZmE4Yz... ) Re: Default behavior for datatype Instant with a Oracle database does not behave as expected. ( https://hibernate.atlassian.net/browse/HHH-17051?atlOrigin=eyJpIjoiZmE4Yz... ) Like I wrote on one of your PRs ( https://github.com/hibernate/hibernate-test-case-templates/pull/302#discu... ) , this is expected. Read the migration guide entry ( https://github.com/hibernate/hibernate-orm/blob/6.0/migration-guide.adoc#... ) about this change. > > > > Specifying a custom column definition is already asking for trouble. I > think that the TIMESTAMP_UTC type expects timestamp with time zone , so if > you want to use a different DDL type, I think you'll have to annotate this > with @JdbcTypeCode(SqlTypes.TIMESTAMP) or change the config like you > described in your readme. > > ( 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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100234- sha1:9e2db29 )

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-17052) When doing an entityManager find with an entity graph the pulled data does not have the entity loaded unless the existing entity is detached

by Archimedes Trajano (JIRA)

Archimedes Trajano ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZDE5YjYyM2Ix... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-17052?atlOrigin=eyJpIjoiZDE5Yj... ) HHH-17052 ( https://hibernate.atlassian.net/browse/HHH-17052?atlOrigin=eyJpIjoiZDE5Yj... ) When doing an entityManager find with an entity graph the pulled data does not have the entity loaded unless the existing entity is detached ( https://hibernate.atlassian.net/browse/HHH-17052?atlOrigin=eyJpIjoiZDE5Yj... ) Change By: Archimedes Trajano ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I have a code {noformat} // entity is an Entity that contains OneToMany collections // I need this detach() for the following find() to provide me a managed entity that // contains the collections loaded. Otherwise, `loaded` still has the collections uninitialized. entityManager.detach(entity); final var entityType = entityManager.getMetamodel().entity(entity.getClass()); final var entityGraph = entityManager.getEntityGraph(entityType.getName()); final var loaded = entityManager.find( entity.getClass(), entity.getId(), Map.of( SpecHints.HINT_SPEC_LOAD_GRAPH, entityGraph, SpecHints.HINT_SPEC_CACHE_RETRIEVE_MODE, CacheRetrieveMode.BYPASS));{noformat} I put in the workaround I had to do, but ideally it should either replace the {{entity}} with the newly loaded one since it’s managed already when I do the find with the entity graph hint. But ideally I think [Allow passing in an entity graph on EntityManager.refresh · hibernate/hibernate-orm · Discussion #7152 (github.com)|https://github.com/hibernate/hibernate-orm/discussions/7152] would look cleaner. Here is more context of my workaround [java - Hibernate: best practice to pull all lazy collections - Stack Overflow|https://stackoverflow.com/questions/19928568/hibernate-best-prac...] ( https://hibernate.atlassian.net/browse/HHH-17052#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-17052#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100234- sha1:9e2db29 )

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-17052) When doing an entityManager find with an entity graph the pulled data does not have the entity loaded unless the existing entity is detached

by Archimedes Trajano (JIRA)

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-17052) When doing an entityManager find with an entity graph the pulled data does not have the entity loaded unless the existing entity is detached

by Archimedes Trajano (JIRA)

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-17051) Default behavior for datatype Instant with a Oracle database does not behave as expected.

by Madeleine Andersson (JIRA)

Madeleine Andersson ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNmVjYjVkNzE5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-17051?atlOrigin=eyJpIjoiNmVjYj... ) HHH-17051 ( https://hibernate.atlassian.net/browse/HHH-17051?atlOrigin=eyJpIjoiNmVjYj... ) Default behavior for datatype Instant with a Oracle database does not behave as expected. ( https://hibernate.atlassian.net/browse/HHH-17051?atlOrigin=eyJpIjoiNmVjYj... ) Change By: 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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100234- sha1:9e2db29 )

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-17051) Default behavior for datatype Instant with a Oracle database does not behave as expected.

by Madeleine Andersson (JIRA)

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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100234- sha1:9e2db29 )

1 year, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2023