March 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16259) Consider jakarta.persistence.database-product-name for SessionFactory dialect resolution when using hibernate.temp.use_jdbc_metadata_defaults=false and versions are not provided

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16259 ( https://hibernate.atlassian.net/browse/HHH-16259?atlOrigin=eyJpIjoiNzliZj... ) Re: Consider jakarta.persistence.database-product-name for SessionFactory dialect resolution when using hibernate.temp.use_jdbc_metadata_defaults=false and versions are not provided ( https://hibernate.atlassian.net/browse/HHH-16259?atlOrigin=eyJpIjoiNzliZj... ) Like we discussed on Zulip, I think the ability to ask for the minimum version explicitly using jakarta.persistence.database-product-version is the best option. E.g. jakarta.persistence.database-product-name=postgresql jakarta.persistence.database-product-version=minimum ( https://hibernate.atlassian.net/browse/HHH-16259#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16259#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#100217- sha1:45db922 )

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16237) versionUpdateGroup is null for Enity extending another Entity when only ElementCollection is updated.

by Marco Belladelli (JIRA)

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16259) Consider jakarta.persistence.database-product-name for SessionFactory dialect resolution when using hibernate.temp.use_jdbc_metadata_defaults=false and versions are not provided

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYTUxYTlhZjIy... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16259?atlOrigin=eyJpIjoiYTUxYT... ) HHH-16259 ( https://hibernate.atlassian.net/browse/HHH-16259?atlOrigin=eyJpIjoiYTUxYT... ) Consider jakarta.persistence.database-product-name for SessionFactory dialect resolution when using hibernate.temp.use_jdbc_metadata_defaults=false and versions are not provided ( https://hibernate.atlassian.net/browse/HHH-16259?atlOrigin=eyJpIjoiYTUxYT... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) At the moment, when using {{hibernate.temp.use_jdbc_metadata_defaults=false}} and database (e.g. {{jakarta.persistence.database-product-version}} versions are not set), the dialect can only be configured through setting {{hibernate.dialect}} to an explicit dialect class. It would be nice to allow dialect resolution based on {{jakarta.persistence.database-product-name}} only, and use Hibernate ORM’s own defaults for dialect versions in that case when {{jakarta. persistence.database-product-version}} is not set and {{hibernate.temp.use_jdbc_metadata_defaults=false}}. ( https://hibernate.atlassian.net/browse/HHH-16259#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16259#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#100217- sha1:45db922 )

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16262) Entities with recursive associations not loaded using EntityGraph

by Florence Watry (JIRA)

Florence Watry ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=639ae0f... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzY3YjQyOWY5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16262?atlOrigin=eyJpIjoiMzY3Yj... ) HHH-16262 ( https://hibernate.atlassian.net/browse/HHH-16262?atlOrigin=eyJpIjoiMzY3Yj... ) Entities with recursive associations not loaded using EntityGraph ( https://hibernate.atlassian.net/browse/HHH-16262?atlOrigin=eyJpIjoiMzY3Yj... ) Issue Type: Bug Affects Versions: 6.1.7 Assignee: Unassigned Created: 07/Mar/2023 05:51 AM Priority: Major Reporter: Florence Watry ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=639ae0f... ) Issue encountered when migrating from Hibernate 5.4.10.Final to 6.1.7.Final. We have entities with recursive associations and we want to fetch 3 levels of parents using entity graph, but the last parent is never initialized : if the entity has only 2 levels of parent then the second isn’t fetched , if it has 3, then the third isn’t fetched. Here’s the test case for Hibernate 6.1.7.Final (the test fails also for 6.2.0.CR3 ): https://github.com/FloWat/graph_recursive_association_h6/blob/main/src/te... ( https://github.com/FloWat/graph_recursive_association_h6/blob/main/src/te... ) And the test case for Hibernate 5.4.10.Final (the test passes also on 5.6.15.Final ) : https://github.com/FloWat/graph_recursive_association_h5/blob/main/src/te... ( https://github.com/FloWat/graph_recursive_association_h5/blob/main/src/te... ) ( https://hibernate.atlassian.net/browse/HHH-16262#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16262#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#100217- sha1:45db922 )

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16249) StatelessSession does not flush when using jdbc batch_size > 1

by Felix König (JIRA)

Felix König ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a4bad5... ) *commented* on HHH-16249 ( https://hibernate.atlassian.net/browse/HHH-16249?atlOrigin=eyJpIjoiZTViMz... ) Re: StatelessSession does not flush when using jdbc batch_size > 1 ( https://hibernate.atlassian.net/browse/HHH-16249?atlOrigin=eyJpIjoiZTViMz... ) Hey there, > > > > For [the last round of statements to not get flushed] to happen, the > inserts need to be inside in a transaction opened by the stateless session > > > I am not sure why this is a requirement. In fact, using the stateless session the “conventional way”, meaning purely within a transaction managed by the stateless session, works fine for all jdbc batch sizes: statelessSession.getTransaction().begin(); // do stuff statelessSession.getTransaction().commit(); But in the example I provided, the batch size is 2, and the third entity is lost (the test fails). ( https://hibernate.atlassian.net/browse/HHH-16249#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16249#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#100217- sha1:45db922 )

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16215) Composite primary key @IdClass attribute mapping is borrowed from the first OneToMany backref and cannot be set

by Marco Belladelli (JIRA)

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16261) JPA metamodel generator is not considering Java 14's records

by Sven Linstaedt (JIRA)

Sven Linstaedt ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzE5YzBjMDdk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16261?atlOrigin=eyJpIjoiYzE5Yz... ) HHH-16261 ( https://hibernate.atlassian.net/browse/HHH-16261?atlOrigin=eyJpIjoiYzE5Yz... ) JPA metamodel generator is not considering Java 14's records ( https://hibernate.atlassian.net/browse/HHH-16261?atlOrigin=eyJpIjoiYzE5Yz... ) Issue Type: Bug Affects Versions: 6.2.0.CR3 Assignee: Unassigned Components: hibernate-jpamodelgen Created: 07/Mar/2023 04:59 AM Priority: Major Reporter: Sven Linstaedt ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Though hibernate 6.2 is supporting mapping of Java records as embeddable types, it’s metamodel generator is not generating anything at all for these records, causing devs relying mostly on the criteria API for complex query building not being able to use records for that purpose. ( https://hibernate.atlassian.net/browse/HHH-16261#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16261#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#100217- sha1:45db922 )

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16260) JdbcParameterRenderer not called with dynamic filters

by Davide D'Alto (JIRA)

Davide D'Alto ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZDA2Nzc4ODJm... ) / New Feature ( https://hibernate.atlassian.net/browse/HHH-16260?atlOrigin=eyJpIjoiZDA2Nz... ) HHH-16260 ( https://hibernate.atlassian.net/browse/HHH-16260?atlOrigin=eyJpIjoiZDA2Nz... ) JdbcParameterRenderer not called with dynamic filters ( https://hibernate.atlassian.net/browse/HHH-16260?atlOrigin=eyJpIjoiZDA2Nz... ) Change By: Davide D'Alto ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Example of mapping that skips the JdbcParameterRenderer: {code:java} @FilterDef(name = "current", defaultCondition = "deleted = false") @FilterDef(name = "region", defaultCondition = "region = :region", parameters = @ParamDef(name = "region", type = org.hibernate.type.descriptor.java.StringJavaType.class)) @Entity(name = "Element") @Table(name = "Element") @Filter(name = "current") @Filter(name = "region") public static class Element { ... }{code} A test class is availble on my repository: [https://github.com/DavideD/hibernate-orm/blob/filterTest/hibernate-core/s...] It’s possible to see in [FilterHelper|https://github.com/hibernate/hibernate-orm/blob/main/hiberna...] that the renderer is never called when parameters are required. ( https://hibernate.atlassian.net/browse/HHH-16260#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16260#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#100217- sha1:45db922 )

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-16212) UnknownTableReferenceException with one-to-many relationship mapped by another entity

by Steve Webber (JIRA)

Steve Webber ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63f359a... ) *commented* on HHH-16212 ( https://hibernate.atlassian.net/browse/HHH-16212?atlOrigin=eyJpIjoiZWU3N2... ) Re: UnknownTableReferenceException with one-to-many relationship mapped by another entity ( https://hibernate.atlassian.net/browse/HHH-16212?atlOrigin=eyJpIjoiZWU3N2... ) Hello Thank you for your reply. If my test case does not represent valid behaviour then I’m happy for this issue to be closed. I do feel it is inconsistent given that: * It did work in hibernate-core 5.6.15.Final - for an example see: https://github.com/s-webber/hibernate-test-case-orm-5-subselect-unknown-t... ( https://github.com/s-webber/hibernate-test-case-orm-5-subselect-unknown-t... ) * It continues to work in hibernate-core 6.1.7.Final if I alter TableOneEntity to use FetchMode.SELECT instead of FetchMode.SUBSELECT. ( https://hibernate.atlassian.net/browse/HHH-16212#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16212#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#100217- sha1:45db922 )

1 year, 10 months

1
0
0 / 0

[JIRA] (HHH-13664) SimpleTimestamper hangs in loop when system clock jumps backwards

by Irina Tarasenko (JIRA)

Irina Tarasenko ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5d26db7... ) *commented* on HHH-13664 ( https://hibernate.atlassian.net/browse/HHH-13664?atlOrigin=eyJpIjoiNzIyOW... ) Re: SimpleTimestamper hangs in loop when system clock jumps backwards ( https://hibernate.atlassian.net/browse/HHH-13664?atlOrigin=eyJpIjoiNzIyOW... ) hi, disabling Second level cache in Hibernate solved this issue: jpaPropertyMap.put("hibernate.cache.region.factory_class","com.hazelcast.hibernate.HazelcastCacheRegionFactory"); jpaPropertyMap.put("hibernate.cache.use_second_level_cache", "false"); jpaPropertyMap.put("hibernate.cache.use_query_cache", "false"); Now it is just never enters into SimpleTimestamper.java. ( https://hibernate.atlassian.net/browse/HHH-13664#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13664#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#100217- sha1:45db922 )

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