June 2023 - hibernate-issues - Jboss List Archives

Michael Musenbrock ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNDkzYzBmY2Nj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16828?atlOrigin=eyJpIjoiNDkzYz... ) HHH-16828 ( https://hibernate.atlassian.net/browse/HHH-16828?atlOrigin=eyJpIjoiNDkzYz... ) CriteriaBuilder.equal(Expression any, null object): QueryException: Ordinal parameter not bound ( https://hibernate.atlassian.net/browse/HHH-16828?atlOrigin=eyJpIjoiNDkzYz... ) Issue Type: Bug Affects Versions: 6.0.0, 6.1.5 Assignee: Unassigned Components: hibernate-core, query-criteria Created: 20/Jun/2023 08:25 AM Environment: Alpine 3.17, Eclipse Temurin 17.0.7, Wildfly 27.0.1, Hibernate 6.1.5.Final Priority: Major Reporter: Michael Musenbrock ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) Hi, we are currently migrating our code from JavaEE 8 to Jakarta EE 10 and therefore we also migrate from Hibernate 5 to Hibernate 6. Our repository-classes mostly rely on the Criteria API. We now experience a ‘QueryException: Ordinal parameter not bound’ if the caller passes in null-reference to methods using: cb.equal(root.get(ClassXX.field), null-reference); in the WHERE clause. In Hibernate 5 this was working and seemed to produced a UNKOWN result and therefore returning an empty result (if only that condition was used). In Hibernate 6 (6.1.5) a null-value is not added to the parameterBindings in the QuerySqmImpl ( https://github.com/hibernate/hibernate-orm/blob/527bdbdaf578cb3ec0abb9d74... ) and therefore results in a QueryParameterException once the queryParameters are validated ( https://github.com/hibernate/hibernate-orm/blob/527bdbdaf578cb3ec0abb9d74... ). The JPA 3.1 Specification for Input Parameters ( https://jakarta.ee/specifications/persistence/3.1/jakarta-persistence-spe... ) only states that if the input parameter is null it will yield an unkown value. UNKOWN is fine, but I would not expect an Exception here. From the code it seems that Hibernate 6.2 will throw a different message for the QueryParameterException. I will try to set-up a small project to demonstrate the behavior. regards Michael ( https://hibernate.atlassian.net/browse/HHH-16828#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16828#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#100227- sha1:8ffa416 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16745) TransientObjectException when loading versioned entity from second-level cache with @OneToOne LAZY mapping

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16745 ( https://hibernate.atlassian.net/browse/HHH-16745?atlOrigin=eyJpIjoiMDljZD... ) Re: TransientObjectException when loading versioned entity from second-level cache with @OneToOne LAZY mapping ( https://hibernate.atlassian.net/browse/HHH-16745?atlOrigin=eyJpIjoiMDljZD... ) I’m sorry but without a reproducer it would be hard for us to tell what’s going on and what’s causing the issue. Maybe reach out to the Spring folks it the problem only occurs when that framework is involved, and feel free to open a new issue here if you can identify a problem with Hibernate. ( https://hibernate.atlassian.net/browse/HHH-16745#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16745#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#100227- sha1:8ffa416 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16581) in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup

by Oleksii Miroshnyk (JIRA)

Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) *commented* on HHH-16581 ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiYWU4M2... ) Re: in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiYWU4M2... ) >>There should be exactly one definition of every filter. I would agree, but the thing is that hibernate is pretty widely used and it is here for a while, and with such kind of drastic change an effort of maintaining & upgrading legacy applications increases significantly. Not saying that idea of defining something in ONE class/entity that is applied across ALL entities is not that straightforward, so I don’t see nothing bad if it will be “duplicated”. The better idea would be probably to move filter definition to some more distinct place like some config xml or any other place that is considered as a singleton per persistence unit, but with the current design I would vote to follow the approach that was there from the very beginning. ( https://hibernate.atlassian.net/browse/HHH-16581#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16581#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#100227- sha1:8ffa416 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16798) ClassCastException in Hibernate 6 when "join fetch" is used in a query with entity inheritance

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16798 ( https://hibernate.atlassian.net/browse/HHH-16798?atlOrigin=eyJpIjoiOWJmNj... ) Re: ClassCastException in Hibernate 6 when "join fetch" is used in a query with entity inheritance ( https://hibernate.atlassian.net/browse/HHH-16798?atlOrigin=eyJpIjoiOWJmNj... ) This might be related to https://hibernate.atlassian.net/browse/HHH-16494 , as that issue is meant to address implicitly treated joins (i.e. that use subtypes without an explicit treat in the query) correctly. ( https://hibernate.atlassian.net/browse/HHH-16798#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16798#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#100227- sha1:8ffa416 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16581) in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16581 ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiODI3YT... ) Re: in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiODI3YT... ) I am against this change. There should be exactly one definition of every filter. ( https://hibernate.atlassian.net/browse/HHH-16581#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16581#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#100227- sha1:8ffa416 )

1 year, 3 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 June 2023