June 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16859) max() doesn't work with Enums

by Michał Maliszewski (JIRA)

Michał Maliszewski ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ad7619... ) *commented* on HHH-16859 ( https://hibernate.atlassian.net/browse/HHH-16859?atlOrigin=eyJpIjoiM2NhMz... ) Re: max() doesn't work with Enums ( https://hibernate.atlassian.net/browse/HHH-16859?atlOrigin=eyJpIjoiM2NhMz... ) > > > > (…) if you map them with @Enumerated(STRING) , which is the mapping I think > is strongly preferable. > > I would not agree that the String type of enum is strongly preferred. Whenever there is a need for high performance or the size of the stored data is important then ordinals are preferred over string representation. I take the point that it does not make sense when the enum is stored as a String: @Column(name = "SOME_ENUM" ) @Enumerated(EnumType.STRING) private ESomeEnum type; but here again is a question about consistency: enum = int // legal enum = enum // also legal, no matter if stored as a STRING or ORDINAL. > > > > And, for the record, we’re totally within our rights to make deliberate > changes like this in a major version > > Of course you have right to do any incompatible changes between major versions. You can even not write anything in the manuals or other documentation, but that doesn’t make Hibernate any better. There will be large projects migration soon, and you will have to face those if you decide to not take any actions. There is plenty of use cases where even: enum > 1 makes a lot of sense (simplest case: where every version is a single enum value and you want collect all data with version > x). > > > > I frankly don’t even know what the big deal is when there’s a rather > trivial and perfectly natural workaround: max(cast(enum as Integer)). > > The problem is not about the workaround, the real effort is to change the APIs that expects enum from the query as it was previously possible for 5.x series. It makes it even worse that Hibernate does not throw the exception as long as you don’t use the query. For the large projects it might be quite some effort. ( https://hibernate.atlassian.net/browse/HHH-16859#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16859#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#100227- sha1:534ec1c )

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-16857) JdbcLiteralFormatterCharacterData's lowercase 'n' causes invalid SQL syntax

by Christian Beikov (JIRA)

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-15752) BOOLEAN datatype

by Loïc Lefèvre (JIRA)

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-16856) Hibernate incorrectly does regular JOIN instead of LEFT JOIN when moving from Spring Boot 3.1.0 to 3.1.1

by Andrea Boriero (JIRA)

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-16856) Hibernate incorrectly does regular JOIN instead of LEFT JOIN when moving from Spring Boot 3.1.0 to 3.1.1

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16856 ( https://hibernate.atlassian.net/browse/HHH-16856?atlOrigin=eyJpIjoiMTc1OG... ) Re: Hibernate incorrectly does regular JOIN instead of LEFT JOIN when moving from Spring Boot 3.1.0 to 3.1.1 ( https://hibernate.atlassian.net/browse/HHH-16856?atlOrigin=eyJpIjoiMTc1OG... ) Hi Aleksandr B. ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) , thanks for spotting the cause of this issue. Sebastiaan van den Broek ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I’m going to close this Jira. ( https://hibernate.atlassian.net/browse/HHH-16856#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16856#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#100227- sha1:534ec1c )

1 year, 6 months

1
0
0 / 0

[JIRA] (HSEARCH-4755) Upgrade to Spring Boot 3 for -orm6 artifacts

by Marko Bekhta (JIRA)

Marko Bekhta ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-4755 ( https://hibernate.atlassian.net/browse/HSEARCH-4755?atlOrigin=eyJpIjoiYWU... ) Re: Upgrade to Spring Boot 3 for -orm6 artifacts ( https://hibernate.atlassian.net/browse/HSEARCH-4755?atlOrigin=eyJpIjoiYWU... ) Looks like they actually did! https://www.atomikos.com/Blog/ExtremeTransactions6dot0#Feature199869_Spri... I’ll take a look if we can make use of it 🙂 ( https://hibernate.atlassian.net/browse/HSEARCH-4755#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4755#add-comment?atlOrigin... ) 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#100227- sha1:534ec1c )

1 year, 6 months

1
0
0 / 0

[JIRA] (HSEARCH-4755) Upgrade to Spring Boot 3 for -orm6 artifacts

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-4755 ( https://hibernate.atlassian.net/browse/HSEARCH-4755?atlOrigin=eyJpIjoiMTg... ) Re: Upgrade to Spring Boot 3 for -orm6 artifacts ( https://hibernate.atlassian.net/browse/HSEARCH-4755?atlOrigin=eyJpIjoiMTg... ) Did you look into whether Atomikos or any alternative upgraded to Jakarta? ( https://hibernate.atlassian.net/browse/HSEARCH-4755#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4755#add-comment?atlOrigin... ) 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#100227- sha1:534ec1c )

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-16856) Hibernate incorrectly does regular JOIN instead of LEFT JOIN when moving from Spring Boot 3.1.0 to 3.1.1

by Sebastiaan van den Broek (JIRA)

Sebastiaan van den Broek ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16856 ( https://hibernate.atlassian.net/browse/HHH-16856?atlOrigin=eyJpIjoiNWJiMG... ) Re: Hibernate incorrectly does regular JOIN instead of LEFT JOIN when moving from Spring Boot 3.1.0 to 3.1.1 ( https://hibernate.atlassian.net/browse/HHH-16856?atlOrigin=eyJpIjoiNWJiMG... ) Oh I had no idea this part would be generated by Spring and not Hibernate, or that Spring Data defined queries themselves at all. It’s still an odd change to make in a patch release from 3.1.0 to 3.1.1 though, it definitely worked before. And I would consider it a bug Spring Data generates a regular JOIN because that actually restricts the data, it can’t know if that was the intention or not. That was the entire reason we added the LEFT JOIN manually in the first place. But I can take it up with them then. ( https://hibernate.atlassian.net/browse/HHH-16856#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16856#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#100227- sha1:534ec1c )

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-16861) HQL ordinal() function

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzUwM2I1NDJh... ) / New Feature ( https://hibernate.atlassian.net/browse/HHH-16861?atlOrigin=eyJpIjoiYzUwM2... ) HHH-16861 ( https://hibernate.atlassian.net/browse/HHH-16861?atlOrigin=eyJpIjoiYzUwM2... ) HQL ordinal() function ( https://hibernate.atlassian.net/browse/HHH-16861?atlOrigin=eyJpIjoiYzUwM2... ) Change By: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Several users have complained that in H6 we’re a bit fussier with what you can do with enum types in HQL. They would like us to do an automatic type conversion enum → integer when the enum is mapped {{ORDINAL}}. I’m really not keen on stuff like {{max(enum)}} because it seems quite unnatural to me, and is very sensitive to the details of how the enum is mapped. You _can_ currently write {{max(cast(enum as Integer))}} which seems fine, but I but a little verbose, perhaps. But what if we introduced an explicit function for this, say {{ordinal(enum)}}? * It would be an explicit type conversion, which I prefer quite strongly. * We could make it work even for enums mapped {{STRING}}, translating it to a {{case}} expression. * It would be less verbose than {{cast(enum as Integer)}}. I doubt that this would be hard to implement. Hell, we could even provide a similar function for mapping an {{ORDINAL}} enum to a string value, though this would be somewhat less useful. ( https://hibernate.atlassian.net/browse/HHH-16861#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16861#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#100227- sha1:534ec1c )

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-16859) max() doesn't work with Enums

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16859 ( https://hibernate.atlassian.net/browse/HHH-16859?atlOrigin=eyJpIjoiMDJjNT... ) Re: max() doesn't work with Enums ( https://hibernate.atlassian.net/browse/HHH-16859?atlOrigin=eyJpIjoiMDJjNT... ) See https://hibernate.atlassian.net/browse/HHH-16861 for a better suggestion of how to “solve” this problem. ( https://hibernate.atlassian.net/browse/HHH-16859#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16859#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#100227- sha1:534ec1c )

1 year, 6 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 June 2023