May 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16661) Filters causes NPE when default schema is set

by Marco Belladelli (JIRA)

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16715) accept value() or element() in place of elements() and key() or index() in place of indices()

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16715 ( https://hibernate.atlassian.net/browse/HHH-16715?atlOrigin=eyJpIjoiMGQ3ZT... ) Re: accept value() or element() in place of elements() and key() or index() in place of indices() ( https://hibernate.atlassian.net/browse/HHH-16715?atlOrigin=eyJpIjoiMGQ3ZT... ) OK, so actually we can’t do this because of the following case: max(element(book.tags)) from Book book vs: max(elements(book.tags)) from Book book These actually have different interpretations in HQL today. (The first is an implicit join, the second is an implicit subquery.) But even so, this has led me to some useful cleanups and clarifications. ( https://hibernate.atlassian.net/browse/HHH-16715#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16715#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#100225- sha1:d82e018 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16575) Batch fetch with FlushMode COMMIT overrides/discards dirtied ManyToOne property

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16575 ( https://hibernate.atlassian.net/browse/HHH-16575?atlOrigin=eyJpIjoiODI5MT... ) Re: Batch fetch with FlushMode COMMIT overrides/discards dirtied ManyToOne property ( https://hibernate.atlassian.net/browse/HHH-16575?atlOrigin=eyJpIjoiODI5MT... ) Hi Jones ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) , can you please try if your issue persistes with Hibernate 6.2.3.Final? i tried and your issue seems solved. Thanks! ( https://hibernate.atlassian.net/browse/HHH-16575#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16575#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#100225- sha1:d82e018 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16678) AssertionError in QueryLiteral.<init> when using "update versioned Entity ..." if @Version is a long

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16678 ( https://hibernate.atlassian.net/browse/HHH-16678?atlOrigin=eyJpIjoiNGFmNG... ) Re: AssertionError in QueryLiteral.<init> when using "update versioned Entity ..." if @Version is a long ( https://hibernate.atlassian.net/browse/HHH-16678?atlOrigin=eyJpIjoiNGFmNG... ) Hello Damien GIBOU ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) , after a quick test I believe this was already fixed in 6.2.3. Could you please update to the latest version and verify if the problem persists? ( https://hibernate.atlassian.net/browse/HHH-16678#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16678#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#100225- sha1:d82e018 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16553) StackOverflowError when loading entities chained together

by Andrea Boriero (JIRA)

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16553) StackOverflowError when loading entities chained together

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16553 ( https://hibernate.atlassian.net/browse/HHH-16553?atlOrigin=eyJpIjoiZjZlMG... ) Re: StackOverflowError when loading entities chained together ( https://hibernate.atlassian.net/browse/HHH-16553?atlOrigin=eyJpIjoiZjZlMG... ) Hi Guillaume Toison ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) , tried your test with 5.6 and I have the same failure with @Proxy(lazy=false). I’m going to close this Jira. ( https://hibernate.atlassian.net/browse/HHH-16553#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16553#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#100225- sha1:d82e018 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16673) Fail to get access lazy fetched field ( @ManyToOne ) wich is part of a composite Id (using an @IdClass) when stored in L2 cache

by Erwan Moutymbo (JIRA)

Erwan Moutymbo ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=640210c... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMjEwOGI0Njk0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16673?atlOrigin=eyJpIjoiMjEwOG... ) HHH-16673 ( https://hibernate.atlassian.net/browse/HHH-16673?atlOrigin=eyJpIjoiMjEwOG... ) Fail to get access lazy fetched field ( @ManyToOne ) wich is part of a composite Id (using an @IdClass) when stored in L2 cache ( https://hibernate.atlassian.net/browse/HHH-16673?atlOrigin=eyJpIjoiMjEwOG... ) Change By: Erwan Moutymbo ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=640210c... ) Environment: Hibernate: tried 6.1.7.Final to 6.2.3.Final initially found with Postgresql: 14.5 reproduced with h2 2.1.214 Spring Data JPA: 3.0.6 Spring Boot: 3.0.7 ehcache 3.10.8 JDK: Oracle OpenJDK 64-Bit Server VM Temurin- 17.0. 2 6 OS: Fedora 38 ( https://hibernate.atlassian.net/browse/HHH-16673#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16673#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#100225- sha1:d82e018 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16713) Bogus warning : "HHH100001: JDBC driver did not return the expected number of row counts...."

by Nemanja Jovanovic (JIRA)

Nemanja Jovanovic ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMGExOWIyNmI1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16713?atlOrigin=eyJpIjoiMGExOW... ) HHH-16713 ( https://hibernate.atlassian.net/browse/HHH-16713?atlOrigin=eyJpIjoiMGExOW... ) Bogus warning : "HHH100001: JDBC driver did not return the expected number of row counts...." ( https://hibernate.atlassian.net/browse/HHH-16713?atlOrigin=eyJpIjoiMGExOW... ) Change By: Nemanja Jovanovic ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When batching is turned on for entities that update multiple tables when updated following warn is logged: {{HHH100001: JDBC driver did not return the expected number of row counts}} Problem is in {{org.hibernate.engine.jdbc.batch.internal.BatchImpl.checkRowCounts}} when determining {{expectedNumberOfCounts}}. In case when we are updating one entity (which will set {{batchPosition}} to 1 ) which for example extends entity with inheritance strategy set to {{InheritanceType.JOINED}} , thus creating two update statements to be executed in DB, {{expectedNumberOfCounts}} will be wrongfully determined to be 0 (1/2) and warning will be logged. This is definitely wrong. Also in {{org.hibernate.engine.jdbc.batch.internal.BatchImpl.checkRowCounts }} when logging warning expected and actual are switched. Attached test case produces warning, see the console after execution Edit: One more thing, in example described above (first entity inheriting other via {{InheritanceType.JOINED}} …) {{org.hibernate.engine.jdbc.batch.internal.BatchImpl.checkRowCounts}} is called only for table of entity being updated, it seems it should be called a second time for superclass entity. ( https://hibernate.atlassian.net/browse/HHH-16713#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16713#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#100225- sha1:d82e018 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16714) Caching does not work properly when hibernate.cache.use_structured_entries is turned on

by Andrea Boriero (JIRA)

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16672) Locking entities created in the same transaction fails

by DM (JIRA)

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 May 2023