May 2023 - hibernate-issues - Jboss List Archives

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

by Nemanja Jovanovic (JIRA)

1 year, 5 months

1
0
0 / 0

[JIRA] (HHH-16379) @DynamicUpdate and 'enableDirtyTracking=true' leads to wrong update statement

by Andrea Boriero (JIRA)

1 year, 5 months

1
0
0 / 0

[JIRA] (HHH-16379) @DynamicUpdate and 'enableDirtyTracking=true' leads to wrong update statement

by Andrea Boriero (JIRA)

1 year, 5 months

1
0
0 / 0

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

by Nemanja Jovanovic (JIRA)

Nemanja Jovanovic ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMTdjZWRkYmQw... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16714?atlOrigin=eyJpIjoiMTdjZW... ) HHH-16714 ( https://hibernate.atlassian.net/browse/HHH-16714?atlOrigin=eyJpIjoiMTdjZW... ) Caching does not work properly when hibernate.cache.use_structured_entries is turned on ( https://hibernate.atlassian.net/browse/HHH-16714?atlOrigin=eyJpIjoiMTdjZW... ) Issue Type: Bug Assignee: Unassigned Created: 29/May/2023 09:05 AM Environment: Hibernate 6.2.3.Final (core and jcache), Adoptium 17 JDK, HSQLDB (Used in test case) Priority: Major Reporter: Nemanja Jovanovic ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When hibernate.cache.use_structured_entries is set to true, entities that have superclass are not properly put in cache. Problem is in org.hibernate.sql.results.graph.entity.AbstractEntityInitializer.putInCache , structure from superclass is used for storing cache entry, instead of structure from entity that should be put in cache. This is only a problem when hibernate.cache.use_structured_entries is set to true (see org.hibernate.cache.spi.entry.StructuredCacheEntry.structure vs org.hibernate.cache.spi.entry.UnstructuredCacheEntry.structure ). Gradle test case attached. ( https://hibernate.atlassian.net/browse/HHH-16714#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16714#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:da60ad2 )

1 year, 5 months

1
0
0 / 0

[JIRA] (HHH-16379) @DynamicUpdate and 'enableDirtyTracking=true' leads to wrong update statement

by Andrea Boriero (JIRA)

1 year, 5 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=eyJpIjoiNmFhOTVjNjZi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16713?atlOrigin=eyJpIjoiNmFhOT... ) HHH-16713 ( https://hibernate.atlassian.net/browse/HHH-16713?atlOrigin=eyJpIjoiNmFhOT... ) Bogus warning : "HHH100001: JDBC driver did not return the expected number of row counts...." ( https://hibernate.atlassian.net/browse/HHH-16713?atlOrigin=eyJpIjoiNmFhOT... ) 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 seems to be a bug 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 ( 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:85acc52 )

1 year, 5 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=eyJpIjoiNjg4ZTJkZTg4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16713?atlOrigin=eyJpIjoiNjg4ZT... ) HHH-16713 ( https://hibernate.atlassian.net/browse/HHH-16713?atlOrigin=eyJpIjoiNjg4ZT... ) Bogus warning : "HHH100001: JDBC driver did not return the expected number of row counts...." ( https://hibernate.atlassian.net/browse/HHH-16713?atlOrigin=eyJpIjoiNjg4ZT... ) 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 seems to be a bug. 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 ( 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:da60ad2 )

1 year, 5 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)

1 year, 5 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%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYWExNTFlYjky... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16713?atlOrigin=eyJpIjoiYWExNT... ) HHH-16713 ( https://hibernate.atlassian.net/browse/HHH-16713?atlOrigin=eyJpIjoiYWExNT... ) Bogus warning : "HHH100001: JDBC driver did not return the expected number of row counts...." ( https://hibernate.atlassian.net/browse/HHH-16713?atlOrigin=eyJpIjoiYWExNT... ) Issue Type: Bug Affects Versions: 6.2.3 Assignee: Unassigned Created: 29/May/2023 08:29 AM Environment: Hibernate 6.2.3.Final, Adoptium 17 JDK, HSQL(used in test) Priority: Minor Reporter: 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 seems to be a bug. Also in {{org.hibernate.engine.jdbc.batch.internal.BatchImpl.checkRowCounts }} when logging warning expected and actual are switched. ( 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:85acc52 )

1 year, 5 months

1
0
0 / 0

[JIRA] (HHH-16540) UnknownTableReferenceException for entity with Embeddable key-value in map

by Marco Belladelli (JIRA)

1 year, 5 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