July 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16951) HQL no longer deals with empty collections as bind values for nullness predicates in junction with other predicates

by Alex Nistico (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16951) HQL no longer deals with empty collections as bind values for nullness predicates

by Alex Nistico (JIRA)

Alex Nistico ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiM2EzNjFmZDM0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16951?atlOrigin=eyJpIjoiM2EzNj... ) HHH-16951 ( https://hibernate.atlassian.net/browse/HHH-16951?atlOrigin=eyJpIjoiM2EzNj... ) HQL no longer deals with empty collections as bind values for nullness predicates ( https://hibernate.atlassian.net/browse/HHH-16951?atlOrigin=eyJpIjoiM2EzNj... ) Change By: Alex Nistico ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Named parameters that accepts collections and are used in nullness predicates, fail to bind the value breaking the generated SQL query. For example {noformat}from MarketValue where :codes is null{noformat} Will be translated to {noformat}select m1_0.id,m1_0.code from market_value m1_0 where{noformat} If you bind an empty collectino to :codes The expected translation would be: {noformat}select m1_0.id,m1_0.code from market_value m1_0 where ? is null{noformat} Attached is a minimal reproduction project ( https://hibernate.atlassian.net/browse/HHH-16951#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16951#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#100232- sha1:4a3b42c )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16952) Bytecode enhancement now requires embedded component to be @Embeddable

by Guillaume Toison (JIRA)

Guillaume Toison ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzM4NWQxMTQ0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16952?atlOrigin=eyJpIjoiYzM4NW... ) HHH-16952 ( https://hibernate.atlassian.net/browse/HHH-16952?atlOrigin=eyJpIjoiYzM4NW... ) Bytecode enhancement now requires embedded component to be @Embeddable ( https://hibernate.atlassian.net/browse/HHH-16952?atlOrigin=eyJpIjoiYzM4NW... ) Issue Type: Bug Affects Versions: 6.2.6 Assignee: Unassigned Components: hibernate-core, hibernate-enhance-maven-plugin Created: 18/Jul/2023 00:04 AM Priority: Minor Reporter: Guillaume Toison ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) When upgrading an application from Hibernate 5.6 to 6.2 I ran into an issue where the class corresponding to an @Embedded property was not annotated with @Embeddable I am also using the enhance maven plugin: <plugin> <groupId> org.hibernate.orm.tooling </groupId> <artifactId> hibernate-enhance-maven-plugin </artifactId> <version> ${hibernate.version} </version> <executions> <execution> <configuration> <failOnError> true </failOnError> <enableLazyInitialization> false </enableLazyInitialization> <enableDirtyTracking> true </enableDirtyTracking> <enableAssociationManagement> false </enableAssociationManagement> <enableExtendedEnhancement> false </enableExtendedEnhancement> </configuration> <goals> <goal> enhance </goal> </goals> </execution> </executions> </plugin> With Hibernate 6 this fails at runtime when trying to call the property setter: java.lang.ClassCastException: Object of type 'class abc.MyComponent' can't be cast to CompositeTracker at org.hibernate.engine.internal.ManagedTypeHelper.asCompositeTracker(ManagedTypeHelper.java:337) at abc.MyEntity.$$_hibernate_write_myEmbeddedProperty(MyEntity.java) Unless I’m mistaken it is indeed requirred by the JPA spec that the class is annotated with @Embeddable so it is user error and it is fair enough that it fails. However the error message (and the cause of the problem) was not so obvious to me, I found solution from someone who ran into a similar problem: https://github.com/quarkusio/quarkus/issues/34603 Maybe this should fail at build time, when running the bytecode enhancement? Or maybe the error message could mention @Embeddable as a possible cause for the error? I’ve tried making a unit test reproducing the problem but could not, so maybe I misunderstood the issue. ( https://hibernate.atlassian.net/browse/HHH-16952#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16952#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#100232- sha1:4a3b42c )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16951) HQL no longer deals with empty collections as bind values for nullness predicates

by Alex Nistico (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16951) HQL no longer deals with empty collections as bind values for nullness predicates

by Alex Nistico (JIRA)

Alex Nistico ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiM2VjMTNhM2Zk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16951?atlOrigin=eyJpIjoiM2VjMT... ) HHH-16951 ( https://hibernate.atlassian.net/browse/HHH-16951?atlOrigin=eyJpIjoiM2VjMT... ) HQL no longer deals with empty collections as bind values for nullness predicates ( https://hibernate.atlassian.net/browse/HHH-16951?atlOrigin=eyJpIjoiM2VjMT... ) Issue Type: Bug Affects Versions: 6.2.6 Assignee: Unassigned Components: query-hql Created: 18/Jul/2023 00:02 AM Priority: Major Reporter: Alex Nistico ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Named parameters that accepts collections and are used in nullness predicates, fail to bind the value breaking the generated SQL query. For example from MarketValue where :codes is null Will be translated to select m1_0.id,m1_0.code from market_value m1_0 where If you bind an empty collectino to :codes The expected translation would be: select m1_0.id,m1_0.code from market_value m1_0 where ? is null ( https://hibernate.atlassian.net/browse/HHH-16951#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16951#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#100232- sha1:4a3b42c )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-13866) OneToOne-association produces error on 5.4.0+ when using PostgreSQL

by Jin Kwon (JIRA)

Jin Kwon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13866 ( https://hibernate.atlassian.net/browse/HHH-13866?atlOrigin=eyJpIjoiNDAzYT... ) Re: OneToOne-association produces error on 5.4.0+ when using PostgreSQL ( https://hibernate.atlassian.net/browse/HHH-13866?atlOrigin=eyJpIjoiNDAzYT... ) FYI, changing insertable = true with parent entity produces same result. What a weird solution we have here. https://stackoverflow.com/a/54405532/330457 ( https://hibernate.atlassian.net/browse/HHH-13866#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13866#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#100232- sha1:4a3b42c )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16950) Bump local-build-plugins Jandex version

by Jan Schatteman (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16936) Entity not being removed from persistence context after a delete in JPQL

by Jean-Baptiste Hainaut (JIRA)

Jean-Baptiste Hainaut ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiODcwOGEzNDU4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16936?atlOrigin=eyJpIjoiODcwOG... ) HHH-16936 ( https://hibernate.atlassian.net/browse/HHH-16936?atlOrigin=eyJpIjoiODcwOG... ) Entity not being removed from persistence context after a delete in JPQL ( https://hibernate.atlassian.net/browse/HHH-16936?atlOrigin=eyJpIjoiODcwOG... ) Change By: Jean-Baptiste Hainaut ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) When using a composite id, the entity is not removed from the persistance context with a delete query written in JPQL Our Entity and composite id : {code:java}@Entity @NoArgsConstructor(access = AccessLevel.PRIVATE, force = true) public class SchoolSetting { @EmbeddedId private final SchoolSettingId id; @Getter private boolean activated; public SchoolSetting(@NonNull final String schoolId, @NonNull final String key, final boolean activated) { this.id = new SchoolSettingId(schoolId, key); this.activated = activated; } public String getKey() { return this.id.getKey(); } } @Embeddable @NoArgsConstructor(access = AccessLevel.PRIVATE, force = true) @Getter(AccessLevel.PROTECTED) @EqualsAndHashCode public class SchoolSettingId implements Serializable { private final String schoolId; private final String key; public SchoolSettingId(@NonNull final String schoolId, @NonNull final String key) { this.schoolId = schoolId; this.key = key; } }{code} The repository : {code:java}interface SpringDataSchoolSettingRepository extends CrudRepository<SchoolSetting, SchoolSettingId> { @Query("delete from SchoolSetting s WHERE s.id.key = :id") @Modifying void deleteById(@Param("id") SchoolSettingId id); }{code} The following test fail without the testEntityManager.clear() as the entity is still in the persistence context. We we are able to reproduce the same behavior with production code inside the same transaction {code:java}@DataJpaTest @AutoConfigureTestDatabase(replace = AutoConfigureTestDatabase.Replace.NONE) @Import(JpaSchoolSettingRepository.class) class JpaSchoolSettingRepositoryIT { static String SCHOOL_ID = "MY_SCHOOL"; @Autowired TestEntityManager testEntityManager; @Autowired JpaSchoolSettingRepository jpaSchoolSettingRepository; @Test void deleteTwiceShouldntThrowAnyException() { testEntityManager.persistAndFlush(createSetting()); assertThat(jpaSchoolSettingRepository.get(new SchoolSettingId(SCHOOL_ID, "ABSENCE_FOR_DAY_OFF"))) .isNotEmpty(); jpaSchoolSettingRepository.delete(new SchoolSettingId(SCHOOL_ID, "ABSENCE_FOR_DAY_OFF")); //testEntityManager.clear(); assertThat(jpaSchoolSettingRepository.get(new SchoolSettingId(SCHOOL_ID, "ABSENCE_FOR_DAY_OFF"))) .isEmpty(); assertThatCode(() -> jpaSchoolSettingRepository.delete(new SchoolSettingId(SCHOOL_ID, "ABSENCE_FOR_DAY_OFF"))) .doesNotThrowAnyException(); } private SchoolSetting createSetting() { return new SchoolSetting(SCHOOL_ID, ABSENCE_FOR_DAY_OFF, true); } }{code} the assertion one line 23 fail without the {{testEntityManager.clear()}} ( https://hibernate.atlassian.net/browse/HHH-16936#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16936#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#100232- sha1:33a7c72 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16950) Bump local-build-plugins Jandex version

by Jan Schatteman (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16950) Bump local-build-plugins Jandex version

by Jan Schatteman (JIRA)

2 years, 8 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 July 2023