May 2023 - hibernate-issues - Jboss List Archives

Georg Echterling ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMGI3NDFkMjM5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16670?atlOrigin=eyJpIjoiMGI3ND... ) HHH-16670 ( https://hibernate.atlassian.net/browse/HHH-16670?atlOrigin=eyJpIjoiMGI3ND... ) ENUM column definitions cannot be customized (on MySQL/MariaDB) ( https://hibernate.atlassian.net/browse/HHH-16670?atlOrigin=eyJpIjoiMGI3ND... ) Issue Type: Bug Affects Versions: 6.2.3 Assignee: Unassigned Created: 22/May/2023 09:25 AM Priority: Major Reporter: Georg Echterling ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) 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-16670#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16670#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:bbd69a1 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16669) Batch loading prevents throwing ObjectNotFoundException on initialization of non-existent enhanced entity

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOWNhZmQyNWIy... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16669?atlOrigin=eyJpIjoiOWNhZm... ) HHH-16669 ( https://hibernate.atlassian.net/browse/HHH-16669?atlOrigin=eyJpIjoiOWNhZm... ) Batch loading prevents throwing ObjectNotFoundException on initialization of non-existent enhanced entity ( https://hibernate.atlassian.net/browse/HHH-16669?atlOrigin=eyJpIjoiOWNhZm... ) Change By: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) A load via ‘ {{ getReference ' }} on a non-existent object should eventually lead to an {{ObjectNotFoundException}} when such object’s initializer is triggered. This isn’t currently happening in version {{ 6.2.3.Final }} when batch loading is enabled: the read properties are reported as “ " null ” " and no exception is being thrown. ( https://hibernate.atlassian.net/browse/HHH-16669#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16669#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:bbd69a1 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16669) Batch loading prevents throwing ObjectNotFoundException on initialization of non-existent enhanced entity

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYmNkNDU3ODE1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16669?atlOrigin=eyJpIjoiYmNkND... ) HHH-16669 ( https://hibernate.atlassian.net/browse/HHH-16669?atlOrigin=eyJpIjoiYmNkND... ) Batch loading prevents throwing ObjectNotFoundException on initialization of non-existent enhanced entity ( https://hibernate.atlassian.net/browse/HHH-16669?atlOrigin=eyJpIjoiYmNkND... ) Change By: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) A load via ` ‘ getReference ` ' on a non-existent object should eventually lead to an {{ObjectNotFoundException}} when such object’s initializer is triggered. This isn’t currently happening in version 6.2.3.Final when batch loading is enabled: the read properties are reported as “null” and no exception is being thrown. ( https://hibernate.atlassian.net/browse/HHH-16669#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16669#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:bbd69a1 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HV-1949) Nondeterministic behavior of HibernateValidator (in springboot?) when both annotation and xml-based definition are used

by Marko Bekhta (JIRA)

2 years, 10 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 May 2023