October 2022 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-15628) OneToOne relationship is null when hibernate.max_fetch_depth = 1

by Mike Conner (JIRA)

Mike Conner ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62fe3d3... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOTgwMTczYTIw... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15628?atlOrigin=eyJpIjoiOTgwMT... ) HHH-15628 ( https://hibernate.atlassian.net/browse/HHH-15628?atlOrigin=eyJpIjoiOTgwMT... ) OneToOne relationship is null when hibernate.max_fetch_depth = 1 ( https://hibernate.atlassian.net/browse/HHH-15628?atlOrigin=eyJpIjoiOTgwMT... ) Issue Type: Bug Affects Versions: 6.1.4 Assignee: Unassigned Components: query-hql Created: 25/Oct/2022 11:34 AM Environment: Hibernate 6.1.4, $ java -version openjdk version "17.0.4" 2022-07-19 LTS OpenJDK Runtime Environment Corretto-17.0.4.8.1 (build 17.0.4+8-LTS) OpenJDK 64-Bit Server VM Corretto-17.0.4.8.1 (build 17.0.4+8-LTS, mixed mode, sharing) Originally Oracle 19c, test case using H2: com.h2database:h2:2.1.214 Priority: Major Reporter: Mike Conner ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62fe3d3... ) Given entities: Device, DeviceClientId, DeviceServerId, DevPart Where Device has mappings to the two Device_Xxx_Id entities as: @OneToOne(targetEntity = DevClientId.class, mappedBy = "device", cascade = { CascadeType.ALL }, fetch = FetchType.LAZY) @Cascade(org.hibernate.annotations.CascadeType.ALL) private DevClientId devClientId; And DevPart is mapped as: @OneToMany(targetEntity = DevPart.class, mappedBy = "device", fetch = FetchType.EAGER) private Set<DevPart> devParts; Both The Device_Xxx_Id entities map the Device as: @OneToOne(targetEntity = Device.class, fetch = FetchType.EAGER) @JoinColumn(name = "DEVICE_FK" , nullable = false ) private Device device; if hibernate.max_fetch_depth = 1, then a query of the devices results in the clientId and the serverId being null. even though it executes a query for the both the client a server ids. The attached test case outputs the following error: java.lang.AssertionError at org.junit.Assert.fail(Assert.java:87) at org.junit.Assert.assertTrue(Assert.java:42) at org.junit.Assert.assertNotNull(Assert.java:713) at org.junit.Assert.assertNotNull(Assert.java:723) at org.hibernate.bugs.JPAUnitTestCase.testOneToOneTwoWayMapping(JPAUnitTestCase.java:79) Prior to that, it executes sql to get the clientID and does extract data: 13:12:00.362 [main] DEBUG org.hibernate.SQL - select d1_0.pk, d2_0.pk, d2_0.name, d1_0.name from DEV_CLIENT_ID_T d1_0 join DEVICE_T d2_0 on d2_0.pk=d1_0.DEVICE_FK where d1_0.DEVICE_FK=? 13:12:00.364 [main] TRACE org.hibernate.orm.jdbc.bind - binding parameter [1] as [BIGINT] - [1000] 13:12:00.364 [main] TRACE org.hibernate.orm.jdbc.extract - extracted value ([1] : [BIGINT]) - [1101] 13:12:00.365 [main] TRACE org.hibernate.orm.jdbc.extract - extracted value ([2] : [BIGINT]) - [1000] 13:12:00.365 [main] TRACE org.hibernate.orm.jdbc.extract - extracted value ([3] : [VARCHAR]) - [device1] 13:12:00.365 [main] TRACE org.hibernate.orm.jdbc.extract - extracted value ([4] : [VARCHAR]) - [device1ClientId] but never sets it on the Device. If hibernate.max_fetch_depth is set to 2, then this works. This used to work in 5.3.28. Also, for some reason, if I remove the DevPart class and mapping entirely, the test again fails to load the DevClientID and DevServerID into the Device, but this time it fails regardless of the {{hibernate.max_fetch_depth }}value. ( https://hibernate.atlassian.net/browse/HHH-15628#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15628#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#100209- sha1:9aa9d1d )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15086) Configurable query cache structure layout

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNzUxMTdlNTA3... ) / New Feature ( https://hibernate.atlassian.net/browse/HHH-15086?atlOrigin=eyJpIjoiNzUxMT... ) HHH-15086 ( https://hibernate.atlassian.net/browse/HHH-15086?atlOrigin=eyJpIjoiNzUxMT... ) Configurable query cache structure layout ( https://hibernate.atlassian.net/browse/HHH-15086?atlOrigin=eyJpIjoiNzUxMT... ) Change By: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) In 6.0 we changed the query cache structure so that it contains all the data, whereas in 5.x a cache value for an entity stored only the PK value. Both approaches have advantages and disadvantages, so we should try to provide a way to configure how the cache for an entity should be structured. When we have that, we should enable the test {{org.hibernate.orm.test.jpa.query.CachedQueryTest#testCacheableQuery}} We should always use the shallow layout for entities/associations that use reference caching. ( https://hibernate.atlassian.net/browse/HHH-15086#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15086#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#100209- sha1:9aa9d1d )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15622) Query bug in @NamedEntityGraph when doing Eager loading of @OneToOne mappings in Single Table inheritance

by Andrea Boriero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15622) Query bug in @NamedEntityGraph when doing Eager loading of @OneToOne mappings in Single Table inheritance

by Andrea Boriero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15607) @NamedEntityGraph is not working when try to load Basic attribute with OneToMany relation.

by Andrea Boriero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4731) Run tests against OpenSearch 1.3.6

by Automation for Jira (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4729) Add compatibility with OpenSearch 2.1, 2.2, 2.3

by Automation for Jira (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4730) Remove outdated, incorrect entries from Jenkins CI configuration

by Automation for Jira (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15627) useless error message of multi-@JoinColumn mapping does not specify referencedColumnName

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=eyJpIjoiMjQxZTRjYWJm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15627?atlOrigin=eyJpIjoiMjQxZT... ) HHH-15627 ( https://hibernate.atlassian.net/browse/HHH-15627?atlOrigin=eyJpIjoiMjQxZT... ) useless error message of multi-@JoinColumn mapping does not specify referencedColumnName ( https://hibernate.atlassian.net/browse/HHH-15627?atlOrigin=eyJpIjoiMjQxZT... ) Issue Type: Bug Affects Versions: 6.1.4 Assignee: Unassigned Components: hibernate-core Created: 25/Oct/2022 06:48 AM Priority: Major Reporter: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Consider: @ManyToOne(fetch = FetchType.LAZY) @JoinColumn(name = "ID" , referencedColumnName = "TID" , insertable = false , updatable = false ) @JoinColumn(name = "TOC_ID" , referencedColumnName = "SECTION_ID" , insertable = false , updatable = false ) @JoinColumn(name = "SECTION_NUMBER_NB" , insertable = false , updatable = false ) ReportSection sourceTocSlide; The third resulting @JoinColumn is missing a referencedColumnName (easy to miss). The error is: org.hibernate.MappingException: Logical column name cannot be null That’s … pretty bad. ( https://hibernate.atlassian.net/browse/HHH-15627#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15627#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#100209- sha1:9aa9d1d )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15626) Move old databases to nightly pipeline

by Christian Beikov (JIRA)

2 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2022