January 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-4781) Mention @ScaledNumberField in error messages when the decimal scale cannot be found

by Automation for Jira (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-16053) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inheritance)

by Lukas Witzani (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-16053) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inhertitance)

by Lukas Witzani (JIRA)

Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGE2NWZlMjQ1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiNGE2NW... ) HHH-16053 ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiNGE2NW... ) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inhertitance) ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiNGE2NW... ) Change By: Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) h1. Summary * after updating spring boot to 3.0.1 (which also updates hibernate to 6.1.6.Final) join fetching of nested entities does not work anymore when the nestedEntity reference is in an abstract superclass ("BodyPart") that uses @Inheritance(strategy = InheritanceType.SINGLE_TABLE) * the result is a LazyInitializationException when accessing fields in the nested entity although join fetch has been specified in the @Query h2. 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 * the abstract super class has a nested entity ("NestedEntity") which has some fields !diagram.png|width=614,height=479! h2. Reproduction * [https://github.com/lwitzani/hibernate6JoinFetchIssue|https://github.com/l... are two branches in this repository (one with hibernate 5 and on with hibernate 6) * execute the test PersonPersistenceTest.shouldJoinFetchTheNestedEntitiesOfLegs * the test basically ** creates and saves a Person with one Leg and that Leg has a NestedEntity ** fetches the Person by findByIdJoinFetchLegsWithNestedEntity (a @Query method in the Repository). The query uses join fetch to specify that person->legs is fetched and also that legs->nestedEntity is fetched. ** tries to access the nested entity via person->legs->nestedEntity->name h2. Observations in Hibernate 5.6.14.Final * the query created by findByIdJoinFetchLegsWithNestedEntity is working correct * it join fetches both the body_part and the nested_entity table * it uses a left OUTER join for that * it only defines the clause legs1_.discriminator='LegBodyPart' once !hibernate5_working.png|width=1501,height=926! h2. Observations in Hibernate 6.1.6.Final * the query created by findByIdJoinFetchLegsWithNestedEntity is NOT working correct ** there is no second left join which would join the nested_entity table ** it does NOT use a left join (not outer) ** also, it is strange that there is a duplicate join clause l1_0.discriminator='LegBodyPart' and l1_0.discriminator='LegBodyPart' * result is a LazyInitializationException when accessing the name !hibernate6_failing.png|width=1480,height=926! This issue might be heavily related to [https://hibernate.atlassian.net/browse/HHH-16037|https://hibernate.atlass...] and maybe related to: * [https://hibernate.atlassian.net/browse/HHH-15876|https://hibernate.atlass...] * [https://hibernate.atlassian.net/browse/HHH-15829|https://hibernate.atlass...] ( https://hibernate.atlassian.net/browse/HHH-16053#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16053#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:771690a )

1 year, 8 months

1
0
0 / 0

[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%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMTJkNTk3ZTZk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiMTJkNT... ) HHH-16037 ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiMTJkNT... ) 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=eyJpIjoiMTJkNT... ) Change By: Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) h1. 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 h2. Minimal project for reproduction * [https://github.com/lwitzani/hibernate6_singleTableIssue|https://github.co...] * 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}}) h2. 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 !uml.png|width=517,height=425! h2. 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 h2. 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) !hibernate5.png|width=1265,height=692! h2. 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) !hibernate6.png|width=1179,height=644! h1. Summary * after updating spring boot This issue might be heavily related to 3 [https://hibernate. 0 atlassian. 1 which also updates net/browse/HHH-16053|https:// hibernate to 6. 1 atlassian. 6.Final it does not seem to be possible to update an entity with this constellation net/browse/HHH-16053|smart-link] * the main difference is that an additional and unexpected where clause is added which prevents finding the correct entity in this case maybe related to: * the result is that a new entity is persisted instead of the existing one being updated [https://hibernate.atlassian.net/browse/HHH-15876|https://hibernate.atlass...] * [https://hibernate.atlassian.net/browse/HHH-15829|https://hibernate.atlass...] ( 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:771690a )

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-16053) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inhertitance)

by Lukas Witzani (JIRA)

Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMmYzMGM3NDhl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiMmYzMG... ) HHH-16053 ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiMmYzMG... ) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inhertitance) ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiMmYzMG... ) Change By: Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) h1. Summary * after updating spring boot to 3.0.1 (which also updates hibernate to 6.1.6.Final) join fetching of nested entities does not work anymore when the nestedEntity reference is in an abstract superclass ("BodyPart") that uses @Inheritance(strategy = InheritanceType.SINGLE_TABLE) * the result is a LazyInitializationException when accessing fields in the nested entity although join fetch has been specified in the @Query h2. 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 * the abstract super class has a nested entity ("NestedEntity") which has some fields !diagram.png|width=614,height=479! h2. Reproduction * [https://github.com/lwitzani/hibernate6JoinFetchIssue|https://github.com/l... are two branches in this repository (one with hibernate 5 and on with hibernate 6) * execute the test PersonPersistenceTest.shouldJoinFetchTheNestedEntitiesOfLegs * the test basically ** creates and saves a Person with one Leg and that Leg has a NestedEntity ** fetches the Person by findByIdJoinFetchLegsWithNestedEntity (a @Query method in the Repository). The query uses join fetch to specify that person->legs is fetched and also that legs->nestedEntity is fetched. ** tries to access the nested entity via person->legs->nestedEntity->name h2. Observations in Hibernate 5.6.14.Final * the query created by findByIdJoinFetchLegsWithNestedEntity is working correct * it join fetches both the body_part and the nested_entity table * it uses a left OUTER join for that * it only defines the clause legs1_.discriminator='LegBodyPart' once !hibernate5_working.png|width=1501,height=926! h2. Observations in Hibernate 6.1.6.Final * the query created by findByIdJoinFetchLegsWithNestedEntity is NOT working correct ** there is no second left join which would join the nested_entity table ** it does NOT use a left join (not outer) ** also, it is strange that there is a duplicate join clause l1_0.discriminator='LegBodyPart' and l1_0.discriminator='LegBodyPart' * result is a LazyInitializationException when accessing the name !hibernate6_failing.png|width=1480,height=926! This issue might be heavily related to [https://hibernate.atlassian.net/browse/HHH-16037|https://hibernate.atlass...] and maybe related to: * [https://hibernate.atlassian.net/browse/HHH-15876|https://hibernate.atlass...] * [https://hibernate.atlassian.net/browse/HHH-15829|https://hibernate.atlass...] ( https://hibernate.atlassian.net/browse/HHH-16053#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16053#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:771690a )

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-16053) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inhertitance)

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=eyJpIjoiNTVmZWE4NWVm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiNTVmZW... ) HHH-16053 ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiNTVmZW... ) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inhertitance) ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiNTVmZW... ) Issue Type: Bug Affects Versions: 6.1.6 Assignee: Unassigned Attachments: diagram.png, hibernate5_working.png, hibernate6_failing.png Components: hibernate-core Created: 17/Jan/2023 05:30 AM Environment: Java 17 Spring Boot 3.0.1 Priority: Major Reporter: Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) ******* Summary ******* * after updating spring boot to 3.0.1 (which also updates hibernate to 6.1.6.Final) join fetching of nested entities does not work anymore when the nestedEntity reference is in an abstract superclass ("BodyPart") that uses @Inheritance(strategy = InheritanceType.SINGLE_TABLE) * the result is a LazyInitializationException when accessing fields in the nested entity although join fetch has been specified in the @Query ---------- 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 * the abstract super class has a nested entity ("NestedEntity") which has some fields ------------ Reproduction ------------ * https://github.com/lwitzani/hibernate6JoinFetchIssue ( https://github.com/lwitzani/hibernate6JoinFetchIssue ) there are two branches in this repository (one with hibernate 5 and on with hibernate 6) * execute the test PersonPersistenceTest.shouldJoinFetchTheNestedEntitiesOfLegs * the test basically * creates and saves a Person with one Leg and that Leg has a NestedEntity * fetches the Person by findByIdJoinFetchLegsWithNestedEntity (a @Query method in the Repository). The query uses join fetch to specify that person->legs is fetched and also that legs->nestedEntity is fetched. * tries to access the nested entity via person->legs->nestedEntity->name -------------------------------------- Observations in Hibernate 5.6.14.Final -------------------------------------- * the query created by findByIdJoinFetchLegsWithNestedEntity is working correct * it join fetches both the body_part and the nested_entity table * it uses a left OUTER join for that * it only defines the clause legs1_.discriminator='LegBodyPart' once ( https://hibernate.atlassian.net/secure/attachment/50171/50171_hibernate5_... ) ------------------------------------- Observations in Hibernate 6.1.6.Final ------------------------------------- * the query created by findByIdJoinFetchLegsWithNestedEntity is NOT working correct * there is no second left join which would join the nested_entity table * it does NOT use a left join (not outer) * also, it is strange that there is a duplicate join clause l1_0.discriminator='LegBodyPart' and l1_0.discriminator='LegBodyPart' * result is a LazyInitializationException when accessing the name ( https://hibernate.atlassian.net/secure/attachment/50172/50172_hibernate6_... ) ( https://hibernate.atlassian.net/browse/HHH-16053#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16053#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:771690a )

1 year, 8 months

1
0
0 / 0

[JIRA] (HV-1934) Upgrade to hibernate-asciidoctor-theme 1.0.6

by Yoann Rodière (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HV-1744) Use auto-expanding entries in the documentation TOC

by Yoann Rodière (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-16052) EntityKey and CollectionKey equality optimisation

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiY2VkOGJiZjBm... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16052?atlOrigin=eyJpIjoiY2VkOG... ) HHH-16052 ( https://hibernate.atlassian.net/browse/HHH-16052?atlOrigin=eyJpIjoiY2VkOG... ) EntityKey and CollectionKey equality optimisation ( https://hibernate.atlassian.net/browse/HHH-16052?atlOrigin=eyJpIjoiY2VkOG... ) Issue Type: Improvement Assignee: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: hibernate-core Created: 17/Jan/2023 03:20 AM Environment: Since IdentifierType#isEqual is a megamorphic operation, it's worthwhile attempting to avoid the operation when there's good chances that the IDs are actually the same. This is a fairly common operation and has shown beneficial impact on general performance. Fix Versions: 6.2.0 Labels: performance Priority: Major Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) ( https://hibernate.atlassian.net/browse/HHH-16052#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16052#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:771690a )

1 year, 8 months

1
0
0 / 0

[JIRA] (HSEARCH-4786) Fix non-compiling code in migration guide

by Yoann Rodière (JIRA)

1 year, 8 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