February 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16136) LAZY @ManyToOne may break EAGER @ManyToOne when used on the same entity in a different parent

by Tomas Cerskus (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16135) When owning side of @OneToOne is declared with fetchType.EAGER and not owning side of @OneToOne is declared with fetchType.Lazy the ORM fails to load the mapped entity

by Panagiwths Mpougioukos (JIRA)

Panagiwths Mpougioukos ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63ddac9... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZjcyYTk5ZGNk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16135?atlOrigin=eyJpIjoiZjcyYT... ) HHH-16135 ( https://hibernate.atlassian.net/browse/HHH-16135?atlOrigin=eyJpIjoiZjcyYT... ) When owning side of @OneToOne is declared with fetchType.EAGER and not owning side of @OneToOne is declared with fetchType.Lazy the ORM fails to load the mapped entity ( https://hibernate.atlassian.net/browse/HHH-16135?atlOrigin=eyJpIjoiZjcyYT... ) Change By: Panagiwths Mpougioukos ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63ddac9... ) [https://github.com/de313e/SpringEagerLoadingIssue|https://github.com/de31...] The above contains the test case to verify the bug Possible workaround of issue [https://github.com/de313e/SpringEagerLoadingIssue/pull/2|https://github.c...] The above test case and also workaround in Github is with h2 embedded database. Have tested the same code with local Postgresql database and the behavior is exactly the same. So this should be an issue in ORM layer. Happens only when the *not owning side* has more than 1 fields mapped with {{@OneToOne}} which are declared as {{LAZY}} but from the owner side they are declared as {{EAGER}}. In this example the not owning entity of {{User}} has 2 fields mapped with {{@OneToOne}}, namely {{UserSettings}} and {{UserTermsOfUse}} which are declared as {{LAZY}}. The owning sides of relationship which are {{UserSettings}} and {{UserTermsOfUse}} have a {{EAGER}} relationship with the {{User}} entity. ( https://hibernate.atlassian.net/browse/HHH-16135#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16135#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:6115380 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16136) LAZY @ManyToOne may break EAGER @ManyToOne when used on the same entity in a different parent

by Tomas Cerskus (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16136) LAZY @ManyToOne may break EAGER @ManyToOne when used on the same entity in a different parent

by Tomas Cerskus (JIRA)

Tomas Cerskus ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f3fc10... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMTQyODA3ODVm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16136?atlOrigin=eyJpIjoiMTQyOD... ) HHH-16136 ( https://hibernate.atlassian.net/browse/HHH-16136?atlOrigin=eyJpIjoiMTQyOD... ) LAZY @ManyToOne may break EAGER @ManyToOne when used on the same entity in a different parent ( https://hibernate.atlassian.net/browse/HHH-16136?atlOrigin=eyJpIjoiMTQyOD... ) Change By: Tomas Cerskus ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f3fc10... ) Say I have the following entities {noformat}User { @Id id: String name: String } Order { @Id id: String @ManyToOne(fetch = FetchType.EAGER) @JoinColumn user: User // Meant to be different from Order.user // This extra field makes Hibernate use several queries when fetching which then leads to this bug @ManyToOne(fetch = FetchType.EAGER) @JoinColumn targetUser: User @OneToMany(targetEntity=OrderItem.class, mappedBy="order", fetch=FetchType.EAGER) orderItems: Set<OrderItem> } OrderItem { @Id id: String @ManyToOne(fetch = FetchType.LAZY) @JoinColumn order: Order // Same as Order.user // Note that unlike Order.user, here it is LAZY @ManyToOne(fetch = FetchType.LAZY) @JoinColumn user: User }{noformat} Fetching a single entity works well and returns an Order with all the relationships populated. But fetching multiple entities returns Order with Order.user not initialised. This issue is present with and without bytecode enhancement. - I’ll add a PR with a test case shortly. - - done ( https://hibernate.atlassian.net/browse/HHH-16136#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16136#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:6115380 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16136) LAZY @ManyToOne may break EAGER @ManyToOne when used on the same entity in a different parent

by Tomas Cerskus (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16136) LAZY @ManyToOne may break EAGER @ManyToOne when used on the same entity in a different parent

by tomas (JIRA)

tomas ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f3fc10... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTc0MTZjNzFi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16136?atlOrigin=eyJpIjoiNTc0MT... ) HHH-16136 ( https://hibernate.atlassian.net/browse/HHH-16136?atlOrigin=eyJpIjoiNTc0MT... ) LAZY @ManyToOne may break EAGER @ManyToOne when used on the same entity in a different parent ( https://hibernate.atlassian.net/browse/HHH-16136?atlOrigin=eyJpIjoiNTc0MT... ) Issue Type: Bug Affects Versions: 6.2.0.CR2, 6.1.6 Assignee: Unassigned Created: 04/Feb/2023 04:54 AM Priority: Major Reporter: tomas ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f3fc10... ) Say I have the following entities User { @Id id: String name: String } Order { @Id id: String @ManyToOne(fetch = FetchType.EAGER) @JoinColumn user: User // Meant to be different from Order.user // This extra field makes Hibernate use several queries when fetching which then leads to this bug @ManyToOne(fetch = FetchType.EAGER) @JoinColumn targetUser: User @OneToMany(targetEntity=OrderItem.class, mappedBy="order", fetch=FetchType.EAGER) orderItems: Set<OrderItem> } OrderItem { @Id id: String @ManyToOne(fetch = FetchType.LAZY) @JoinColumn order: Order // Same as Order.user // Note that unlike Order.user, here it is LAZY @ManyToOne(fetch = FetchType.LAZY) @JoinColumn user: User } Fetching a single entity works well and returns an Order with all the relationships populated. But fetching multiple entities returns Order with Order.user not initialised. This issue is present with and without bytecode enhancement. I’ll add a PR with a test case shortly. ( https://hibernate.atlassian.net/browse/HHH-16136#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16136#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:6115380 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15854) Improve CollectionInitializer and EntityDelayedFetchInitializer resolveInstance methods performance when the parent entity is initialized

by Thomas Heigl (JIRA)

Thomas Heigl ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15854 ( https://hibernate.atlassian.net/browse/HHH-15854?atlOrigin=eyJpIjoiMjNjNz... ) Re: Improve CollectionInitializer and EntityDelayedFetchInitializer resolveInstance methods performance when the parent entity is initialized ( https://hibernate.atlassian.net/browse/HHH-15854?atlOrigin=eyJpIjoiMjNjNz... ) I just found the time to run our MassIndexer against Hibernate 6.2.0CR2. Performance is significantly better than 6.1.6, but it is still a lot slower than 5.6.15: *Hibernate 5:* INF MassIndexerImpl Finished updating index in 337s. *Hibernate 6.1.6:* INF MassIndexerImpl Finished updating index in 474s. *Hibernate 6.2.0CR2:* INF MassIndexerImpl Finished updating index in 417s. I’m guessing that most of the additional overhead still comes from fetching entities with associations as documented in the simple performance test in my PRs. ( https://hibernate.atlassian.net/browse/HHH-15854#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15854#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:6115380 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HBX-2480) Reenable disabled tests after the update to ORM 6.2.0.CR2

by Koen Aers (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HBX-2480) Reenable disabled tests after the update to ORM 6.2.0.CR2

by Koen Aers (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16135) When owning side of @OneToOne is declared with fetchType.EAGER and not owning side of @OneToOne is declared with fetchType.Lazy the ORM fails to load the mapped entity

by Panagiwths Mpougioukos (JIRA)

Panagiwths Mpougioukos ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63ddac9... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZGE1YmM3ZmYw... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16135?atlOrigin=eyJpIjoiZGE1Ym... ) HHH-16135 ( https://hibernate.atlassian.net/browse/HHH-16135?atlOrigin=eyJpIjoiZGE1Ym... ) When owning side of @OneToOne is declared with fetchType.EAGER and not owning side of @OneToOne is declared with fetchType.Lazy the ORM fails to load the mapped entity ( https://hibernate.atlassian.net/browse/HHH-16135?atlOrigin=eyJpIjoiZGE1Ym... ) Change By: Panagiwths Mpougioukos ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63ddac9... ) [https://github.com/de313e/SpringEagerLoadingIssue|https://github.com/de31...] The above contains the test case to verify the bug Possible workaround of issue [https://github.com/de313e/SpringEagerLoadingIssue/pull/2|https://github.c...] Happens only when the *not owning side* has more than 1 fields mapped with {{@OneToOne}} which are declared as {{LAZY}} but from the owner side they are declared as {{EAGER}}. In this example the not owning entity of {{User}} has 2 fields mapped with {{@OneToOne}}, namely {{UserSettings}} and {{UserTermsOfUse}} which are declared as {{LAZY}}. The owning sides of relationship which are {{UserSettings}} and {{UserTermsOfUse}} have a {{EAGER}} relationship with the {{User}} entity. ( https://hibernate.atlassian.net/browse/HHH-16135#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16135#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:6115380 )

3 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2023