January 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16037) merge of a persisted entity uses an insert statement instead of an update statement resulting in duplicate entities

by Lukas Witzani (JIRA)

Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYWI2ZjM0MTVj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiYWI2Zj... ) HHH-16037 ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiYWI2Zj... ) merge of a persisted entity uses an insert statement instead of an update statement resulting in duplicate entities ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiYWI2Zj... ) Issue Type: Bug Affects Versions: 6.1.6 Assignee: Unassigned Attachments: hibernate5.png, hibernate6.png, uml.png Components: hibernate-core Created: 13/Jan/2023 01:32 AM Priority: Major Reporter: Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) -------------------------------- Minimal project for reproduction -------------------------------- * https://github.com/lwitzani/hibernate6_singleTableIssue ( https://github.com/lwitzani/hibernate6_singleTableIssue ) * project has two branches (one with hibernate 5 and one with hibernate 6) * the only difference in the branches is the updated versions of spring boot and therefore hibernate * i debugged very deep and think that it is a problem with hibernate at the location where the select statement is generated ( LoaderSelectBuilder. createSelect ) ---------- Requisites ---------- * entity ("Person") exists that has a field which is a set of other entities ("Set\<Leg>") * these other entities are derived from an abstract super class ("Leg extends BodyPart") * the abstract super class' inheritance strategy is SINGLE_TABLE ------------ Reproduction ------------ * execute the test PersonPersistenceTest.shouldUseSQLUpdateToChangeThePersonName * the test basically * creates a Person (without Legs) and saves it using the repository * refetches the Person by findById * changes the Person's name * saves the changed Person again -------------------------------------- Observations in Hibernate 5.6.14.Final -------------------------------------- * when the second save is called (after changing the name) there will be a select statement which is used to check if the entity already exists * the body_part table is joined via left outer join * the where clause here only consists of "where person.id ( http://person.id ) = \<id>" * the entity is correctly found by the select statement so afterwards an update statement follows * result: one entity exists (the changed one) ( https://hibernate.atlassian.net/secure/attachment/50159/50159_hibernate5.png ) ------------------------------------- Observations in Hibernate 6.1.6.Final ------------------------------------- * when the second save is called (after changing the name) there will be a different select statement now * the body_part table is joined via left join now (not outer) * the critical change here is that the where clause now suddenly consists of "where body_part.discriminator = 'LegBodyPart' and person.id ( http://person.id ) = \<id>" * although the entity exists, it is not found by the select statement so afterwards an insert statement follows which creates a second Person with a new id * result: two entities exist (the original one and the changed one) ( https://hibernate.atlassian.net/secure/attachment/50160/50160_hibernate6.png ) ******* Summary ******* * after updating spring boot to 3.0.1 which also updates hibernate to 6.1.6.Final it does not seem to be possible to update an entity with this constellation * the main difference is that an additional and unexpected where clause is added which prevents finding the correct entity in this case * the result is that a new entity is persisted instead of the existing one being updated ( https://hibernate.atlassian.net/browse/HHH-16037#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16037#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#100214- sha1:b03f6a4 )

1 year, 7 months

1
0
0 / 0

[JIRA] (HHH-16036) Fix Oracle CI parameter STATISTICS_LEVEL

by Christian Beikov (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HHH-16036) Fix Oracle CI parameter STATISTICS_LEVEL

by Loïc Lefèvre (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HHH-16036) Fix Oracle CI parameter

by Loïc Lefèvre (JIRA)

Loïc Lefèvre ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOWQxMWE5ZTZj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16036?atlOrigin=eyJpIjoiOWQxMW... ) HHH-16036 ( https://hibernate.atlassian.net/browse/HHH-16036?atlOrigin=eyJpIjoiOWQxMW... ) Fix Oracle CI parameter ( https://hibernate.atlassian.net/browse/HHH-16036?atlOrigin=eyJpIjoiOWQxMW... ) Issue Type: Bug Assignee: Loïc Lefèvre ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: build Created: 13/Jan/2023 01:08 AM Priority: Major Reporter: Loïc Lefèvre ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Strangely, modifying parameter STATISTICS_LEVEL does not work as expected. Instance restart without taking the previous modification of parameter SGA_TARGET into account! Maybe a bug in Oracle 21c XE or a race condition with the GitHub I/O subsystem ( https://hibernate.atlassian.net/browse/HHH-16036#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16036#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#100214- sha1:b03f6a4 )

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-4783) Run more tests for orm6/jakarta artifacts

by Automation for Jira (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-4783) Run more tests for orm6/jakarta artifacts

by Yoann Rodière (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-4783) Run more tests for orm6/jakarta artifacts

by Yoann Rodière (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HHH-16035) Duration literals and 'by' are almost completely broken

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiY2QxMTRjYjQy... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16035?atlOrigin=eyJpIjoiY2QxMT... ) HHH-16035 ( https://hibernate.atlassian.net/browse/HHH-16035?atlOrigin=eyJpIjoiY2QxMT... ) Duration literals and 'by' are almost completely broken ( https://hibernate.atlassian.net/browse/HHH-16035?atlOrigin=eyJpIjoiY2QxMT... ) Issue Type: Bug Assignee: Unassigned Components: hibernate-core Created: 13/Jan/2023 00:23 AM Priority: Major Reporter: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) There is a cluster of bugs around the handling of HQL durations, with literals like 3 day or 5 second and conversions to integer like e.theDuration by second or e.theDuration by day. * On h2, where the storage type for Duration was changed from numeric to interval second , literal durations simply don’t work at all, except in arithmetic expressions, since they need to be rendered as interval ‘3' DAY or interval ‘5' second and instead they’re just rendered as an integer. * But worse, literal durations also seem to be broken on Postgres, where the storage type is numeric(21,0) , apparently as a side effect of the introduction of PostgreSQLIntervalSecondJdbcType. * On databases where getFractionalSecondPrecisionInNanos()!=1 , conversion of a duration to integer using the by operator is completely broken since the value of getFractionalSecondPrecisionInNanos() is simply ignored. (I’m pretty sure this used to work, so I’m not sure what happened here.) * Apparently DB2 doesn’t like {{ {d ‘1974-03-23'} +(2) days}} so we should see if there’s a better way to handle datetime literals on DB2. (This is a very minor issue.) The ironic thing here is that stuff is most broken on Postgres, which is the database we usually test the best. By the way, I question the value of PostgreSQLIntervalSecondJdbcType. What do we even need this for, if we don’t even use interval to store Duration}}s on Postgres? (It looks like we can’t, since {{interval doesn’t have nanosecond precision.) And the implementation is awful reflection-based stuff that probably doesn’t work in Quarkus. I guess I would be inclined to just delete this ugly thing. ( https://hibernate.atlassian.net/browse/HHH-16035#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16035#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#100214- sha1:b03f6a4 )

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-4783) Execute automatic indexing tests with outbox-polling for orm6/jakarta artifacts

by Yoann Rodière (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-4783) Execute automatic indexing tests with outbox-polling for orm6/jakarta artifacts

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiMDBjN2Nj... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-4783?atlOrigin=eyJpIjoiMDB... ) HSEARCH-4783 ( https://hibernate.atlassian.net/browse/HSEARCH-4783?atlOrigin=eyJpIjoiMDB... ) Execute automatic indexing tests with outbox-polling for orm6/jakarta artifacts ( https://hibernate.atlassian.net/browse/HSEARCH-4783?atlOrigin=eyJpIjoiMDB... ) Issue Type: Task Assignee: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: mapper-orm-coordination-outbox-polling Created: 13/Jan/2023 00:20 AM Fix Versions: 6.2-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) It seems the current configuration is incorrect and leading to those tests not being re-executed for outbox-polling coordination. ( https://hibernate.atlassian.net/browse/HSEARCH-4783#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4783#add-comment?atlOrigin... ) 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#100214- sha1:b03f6a4 )

1 year, 7 months

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 January 2023