February 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16198) Fix up TableGroupJoinProducer, et.al.

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNDA1MzE1YmVi... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16198?atlOrigin=eyJpIjoiNDA1Mz... ) HHH-16198 ( https://hibernate.atlassian.net/browse/HHH-16198?atlOrigin=eyJpIjoiNDA1Mz... ) Fix up TableGroupJoinProducer, et.al. ( https://hibernate.atlassian.net/browse/HHH-16198?atlOrigin=eyJpIjoiNDA1Mz... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) A few contracts used during SQL AST creation define overloaded methods where one form accepts a {{SqlAstCreationState}} and is defined as {{default}} calling another form with values extracted from {{SqlAstCreationState}}. E.g. {noformat}public interface TableGroupJoinProducer ... { default TableGroupJoin createTableGroupJoin( NavigablePath navigablePath, TableGroup lhs, String explicitSourceAlias, SqlAstJoinType sqlAstJoinType, boolean fetched, boolean addsPredicate, SqlAstCreationState creationState) { return createTableGroupJoin( navigablePath, lhs, explicitSourceAlias, sqlAstJoinType, fetched, addsPredicate, creationState.getSqlAliasBaseGenerator(), creationState.getSqlExpressionResolver(), creationState.getFromClauseAccess(), creationState.getCreationContext() ); } TableGroupJoin createTableGroupJoin( NavigablePath navigablePath, TableGroup lhs, String explicitSourceAlias, SqlAstJoinType sqlAstJoinType, boolean fetched, boolean addsPredicate, SqlAliasBaseGenerator aliasBaseGenerator, SqlExpressionResolver sqlExpressionResolver, FromClauseAccess fromClauseAccess, SqlAstCreationContext creationContext); }{noformat} The problem is that in a few cases we actually need the {{SqlAstCreationState}} reference within the handling of these calls. A really bad habit I have seen in the code in these cases is to simply pass {{null}} for the {{SqlAstCreationState}} 😞 The “proper” fix would be to address this everywhere to always pass along the {{SqlAstCreationState}}, however that is likely to have a big impact. While all of the affected contracts are incubating we should still try to minimize changes. ( https://hibernate.atlassian.net/browse/HHH-16198#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16198#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#100216- sha1:3fa9804 )

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16198) Fix up TableGroupJoinProducer, et.al.

by Steve Ebersole (JIRA)

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16197) Circular References of the same entity result in different Java Objects when caching enabled and using a query

by Markus Haarländer (JIRA)

Markus Haarländer ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63ef997... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMjI3YmJhZjBj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16197?atlOrigin=eyJpIjoiMjI3Ym... ) HHH-16197 ( https://hibernate.atlassian.net/browse/HHH-16197?atlOrigin=eyJpIjoiMjI3Ym... ) Circular References of the same entity result in different Java Objects when caching enabled and using a query ( https://hibernate.atlassian.net/browse/HHH-16197?atlOrigin=eyJpIjoiMjI3Ym... ) Issue Type: Bug Affects Versions: 6.1.7 Assignee: Unassigned Components: hibernate-jcache Created: 17/Feb/2023 09:19 AM Priority: Major Reporter: Markus Haarländer ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63ef997... ) We switched from Hibernate 5 to 6 and observed a strange behaviour: hibernate 6.1.7 hibernate-jcache 6.1.7 ehcache 3.10.8 Model with a circular reference: Child(id=c1) -> Parent (id=p1) -> Child(id=c1) When using an EntityManager to find the Child with id=c1, everything is fine. Child result = entityManager.find(Child.class, "c1"); The returned result is the same object as the one in result.getParent().getChild(). However, when using a simple query like: Child result = entityManager.createQuery("SELECT child from Child child WHERE child.objectId = 'c1'", Child.class).getSingleResult(); The returned result is a different Java Object than the one in result.getParent().getChild() This leads to huge problems. Please find a testcase here: https://github.com/haarli/hibernate-orm-6 ( https://github.com/haarli/hibernate-orm-6 ) (However, in this test case environment it is not even possible to execute the Query, although it's correct.) If you set "hibernate.cache.use_second_level_cache" to false, everything works fine Thank you for any help. ( https://hibernate.atlassian.net/browse/HHH-16197#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16197#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#100216- sha1:3fa9804 )

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16194) Failure to automatically integrate with Bean Validation is excessively noisy

by Sanne Grinovero (JIRA)

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16196) Coerce literals used in HQL constructor invocation

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMTRjYjAwYWI4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16196?atlOrigin=eyJpIjoiMTRjYj... ) HHH-16196 ( https://hibernate.atlassian.net/browse/HHH-16196?atlOrigin=eyJpIjoiMTRjYj... ) Coerce literals used in HQL constructor invocation ( https://hibernate.atlassian.net/browse/HHH-16196?atlOrigin=eyJpIjoiMTRjYj... ) Issue Type: Bug Affects Versions: 6.2.0.CR2 Assignee: Unassigned Components: hibernate-core Created: 17/Feb/2023 08:34 AM Priority: Major Reporter: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) HQL: select new CatProjectionBean('fake_cat', 'fake_owner', 12.5) from Cat c Java: public CatProjectionBean(String name, String ownerName, Double weight) { } This fails in 6 because 12.5 is parsed as float literal. When parsing a HQL constructor invocation, we should be a bit lenient though and allow parsing the literal also as Double. ( https://hibernate.atlassian.net/browse/HHH-16196#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16196#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#100216- sha1:3fa9804 )

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16195) Hibernate 6 fails to bind appropriate type for mapped superclass with generic attribute

by Jakub (JIRA)

Jakub ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYWIzMDA5NTNk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16195?atlOrigin=eyJpIjoiYWIzMD... ) HHH-16195 ( https://hibernate.atlassian.net/browse/HHH-16195?atlOrigin=eyJpIjoiYWIzMD... ) Hibernate 6 fails to bind appropriate type for mapped superclass with generic attribute ( https://hibernate.atlassian.net/browse/HHH-16195?atlOrigin=eyJpIjoiYWIzMD... ) Issue Type: Bug Affects Versions: 6.2.0.CR2, 6.1.7 Assignee: Unassigned Components: hibernate-entitymanager Created: 17/Feb/2023 07:04 AM Environment: java 17 Priority: Major Reporter: Jakub ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) If a base class (mapped superclass) has a generic attribute and there are more than one subclasses (entities) with different (concrete) attribute types, hibernate 6 will incorrectly use the first (alphabetically) attribute type as required for all entities. This in turn causes an exception when trying to query using the generic attribute. Minimal test case: https://github.com/kuba-wu/h6-demo ( https://github.com/kuba-wu/h6-demo ) This used to work in Hibernate < 6. Issue confirmed with latest stable (6.1.7) and devel (6.2.0.CR2). ( https://hibernate.atlassian.net/browse/HHH-16195#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16195#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#100216- sha1:3fa9804 )

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16194) Failure to automatically integrate with Bean Validation is excessively noisy

by Sanne Grinovero (JIRA)

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16194) Failure to automatically integrate with Bean Validation is excessively noisy

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=eyJpIjoiMTE4YmFmMmMy... ) / Task ( https://hibernate.atlassian.net/browse/HHH-16194?atlOrigin=eyJpIjoiMTE4Ym... ) HHH-16194 ( https://hibernate.atlassian.net/browse/HHH-16194?atlOrigin=eyJpIjoiMTE4Ym... ) Failure to automatically integrate with Bean Validation is excessively noisy ( https://hibernate.atlassian.net/browse/HHH-16194?atlOrigin=eyJpIjoiMTE4Ym... ) Issue Type: Task Assignee: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Created: 17/Feb/2023 06:47 AM Fix Versions: 6.2.0 Priority: Major Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When the BVAL integration is set to auto it attempts to integrate with a Bean Validation implementor, but skip this if there is none available. Currently Hibernate ORM is logging a full stacktrace when the implementation is missing; this is a little concerning and misleading as it’s most likely expected so we should remove the noisy log message. ( https://hibernate.atlassian.net/browse/HHH-16194#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16194#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#100216- sha1:3fa9804 )

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16186) Duplicate entries in OneToMany relation after manual eagerly loading of entries

by T3rm1 (JIRA)

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16193) LazyInitializationException when accessing loaded reference after session is closed using bytecode enhancement

by MK (JIRA)

MK ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZWEzYjBlNjNk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16193?atlOrigin=eyJpIjoiZWEzYj... ) HHH-16193 ( https://hibernate.atlassian.net/browse/HHH-16193?atlOrigin=eyJpIjoiZWEzYj... ) LazyInitializationException when accessing loaded reference after session is closed using bytecode enhancement ( https://hibernate.atlassian.net/browse/HHH-16193?atlOrigin=eyJpIjoiZWEzYj... ) Issue Type: Bug Affects Versions: 6.2.0.CR2 Assignee: Unassigned Attachments: lazy-bytecode-enhancement-error.zip Components: hibernate-enhance-maven-plugin Created: 17/Feb/2023 06:00 AM Environment: The error occurs with 6.2.0.CR2 but not 6.1.7.Final. Priority: Major Reporter: MK ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) A LazyInitializationException occurs when accessing a loaded ManyToOne reference after the session is closed using lazy initialization bytecode enhancement. It only happens in combination with second-level caching and batch size. Entities: @Entity @NamedQueries({ @NamedQuery(name = "PersonType.selectAll" , query = "SELECT a" + " FROM EntityA a" ), }) @Cacheable @Cache(usage = CacheConcurrencyStrategy.READ_WRITE) public class EntityA { @Id @GeneratedValue private Long id; private String name; @ManyToOne private EntityB entityB; } @Entity @BatchSize(size = 500) public class EntityB { @Id @GeneratedValue private Long id; private String name; } Test Code (entities are created beforehand): EntityManager entityManager = entityManagerFactory.createEntityManager(); entityManager.getTransaction().begin(); List<EntityA> aList = entityManager.createNamedQuery( "PersonType.selectAll" , EntityA.class) .getResultList(); entityManager.getTransaction().commit(); entityManager.close(); Assert.assertEquals(1, aList.size()); Assert.assertEquals( "B1" , aList.get(0).getEntityB().getName()); // LazyInitializationException Reproducer is attached! ( https://hibernate.atlassian.net/browse/HHH-16193#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16193#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#100216- sha1:3fa9804 )

1 year, 10 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 February 2023