July 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16995) CLONE - ENUM column definitions cannot be customized (on MySQL/MariaDB)

by Christian Beikov (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16991) EnhancedUserType cannot be used when defining relations

by Andrea Boriero (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16991) EnhancedUserType cannot be used when defining relations

by Andrea Boriero (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16816) Hibernate 6.2 could not execute certain delete statements

by Andrea Boriero (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16816) Hibernate 6.2 could not execute certain delete statements

by Andrea Boriero (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16872) JDBC fetch size seems to be ignored post migration to hibernate6

by Sunil Bm (JIRA)

Sunil Bm ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *commented* on HHH-16872 ( https://hibernate.atlassian.net/browse/HHH-16872?atlOrigin=eyJpIjoiZTNmNz... ) Re: JDBC fetch size seems to be ignored post migration to hibernate6 ( https://hibernate.atlassian.net/browse/HHH-16872?atlOrigin=eyJpIjoiZTNmNz... ) Hey Jan Schatteman, Thanks for fixing the bug !! We verified the fix on 6.2.7.Final version ( https://hibernate.atlassian.net/browse/HHH-16872#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16872#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#100233- sha1:62cfdef )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16991) EnhancedUserType cannot be used when defining relations

by Timon Zilles (JIRA)

Timon Zilles ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16991 ( https://hibernate.atlassian.net/browse/HHH-16991?atlOrigin=eyJpIjoiY2VmZj... ) Re: EnhancedUserType cannot be used when defining relations ( https://hibernate.atlassian.net/browse/HHH-16991?atlOrigin=eyJpIjoiY2VmZj... ) Thank you for the fast response! 👍 I use an H2 database in my reproducer, but you are right. When adding quarkus.hibernate-orm.fetch.batch-size=-1 in the application.properties file in order to deactive the batch loading (as a workaround), the error does not appear anymore. But then the problem is, that now the relation objects are not loaded at all. When I access the getter method of the relation the select query is executed, but I don’t get any result. *The query* Hibernate: select e1_0.a_id, e1_0.id from EntityB e1_0 where e1_0.a_id=? 2023-07-26 10:18:08,264 TRACE [org.hib.orm.jdb.bind] (main) binding parameter [1] as [VARCHAR] - [org.acme.types.StringWrapper@49fb693d] When I select the entities directly, it works as expected. So I assume, that the user type in general works. *Example query (for my reproducer)* public void findEntityAByField() { final var qlString = "SELECT a FROM " + EntityA. class. getName() + " a WHERE a.id = :idField" ; final var query = em.createQuery(qlString, EntityA.class); query.setParameter( "idField" , new StringWrapper( "ID_A_001" )); final var resultList = query.getResultList(); assertEquals(1, resultList.size()); } The query looks like this Hibernate: select e1_0.id from EntityA e1_0 where e1_0.id=? 2023-07-26 10:18:08,452 TRACE [org.hib.orm.jdb.bind] (main) binding parameter [1] as [VARCHAR] - [org.acme.types.StringWrapper@5fe4848] Here I get the entity as expected. As I said, because of this I think the user type works in general. I created a new reproducer for this: https://github.com/timonzi/hibernate-user-type-for-relation-disabled-fetch Am I missing something or is this (another) bug? ( https://hibernate.atlassian.net/browse/HHH-16991#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16991#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#100233- sha1:62cfdef )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16995) CLONE - ENUM column definitions cannot be customized (on MySQL/MariaDB)

by Bosko Popovic (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16995) CLONE - ENUM column definitions cannot be customized (on MySQL/MariaDB)

by Bosko Popovic (JIRA)

Bosko Popovic ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c975d8... ) *commented* on HHH-16995 ( https://hibernate.atlassian.net/browse/HHH-16995?atlOrigin=eyJpIjoiNWE5ZT... ) Re: CLONE - ENUM column definitions cannot be customized (on MySQL/MariaDB) ( https://hibernate.atlassian.net/browse/HHH-16995?atlOrigin=eyJpIjoiNWE5ZT... ) I am making a clone regarding the columDefinition being ignored. There is a coment in the original ticket that issue is fixed in the latest 6.3.0-SNAPSHOT, but it should be fixed in the micro version 6.2.x. Best regards. ( https://hibernate.atlassian.net/browse/HHH-16995#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16995#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#100233- sha1:62cfdef )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16995) CLONE - ENUM column definitions cannot be customized (on MySQL/MariaDB)

by Bosko Popovic (JIRA)

Bosko Popovic ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c975d8... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMWE5OTlkNDVm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16995?atlOrigin=eyJpIjoiMWE5OT... ) HHH-16995 ( https://hibernate.atlassian.net/browse/HHH-16995?atlOrigin=eyJpIjoiMWE5OT... ) CLONE - ENUM column definitions cannot be customized (on MySQL/MariaDB) ( https://hibernate.atlassian.net/browse/HHH-16995?atlOrigin=eyJpIjoiMWE5OT... ) Issue Type: Bug Affects Versions: 6.2.3 Assignee: Unassigned Created: 26/Jul/2023 01:14 AM Priority: Major Reporter: Bosko Popovic ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c975d8... ) https://hibernate.atlassian.net/browse/HHH-15845 changed the generated schema on MySQL/MariaDB when using @Enumerated(EnumType.STRING) to use its enum(...) types. I previously did this manually using @Column(columnDefinition="enum(...)". Now Hibernate ignores my specified column definition for all enum columns. Since the new implementation always sorts the enum values alphapetically (see NamedEnumValueConverter in the 6.2 branch), this makes it impossible to use the intended ordinal-based sorting ( https://mariadb.com/kb/en/enum/#numeric-index ) with the optimized enum types. I haven’t checked the behaviour in the in-development 6.3 version, which changed a lot of the involved code. (See https://hibernate.atlassian.net/browse/HHH-16125 ) Since I haven’t seen any comments about either the sorting behaviour or the columnDefinition overrides, I’m assuming that this hasn’t (intentionally) changed. TLDR: Two behaviours should be fixed: * columnDefinition should always be respected. * enum values should not be sorted alphabetically when generating enum(...) columns in MariaDB/MySQL. ( https://hibernate.atlassian.net/browse/HHH-16995#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16995#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#100233- sha1:62cfdef )

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