June 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-15989) In-line Hibernate settings for sequence and table id generators into mapping XSD

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTZlYzJkNDg5... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15989?atlOrigin=eyJpIjoiNTZlYz... ) HHH-15989 ( https://hibernate.atlassian.net/browse/HHH-15989?atlOrigin=eyJpIjoiNTZlYz... ) In-line Hibernate settings for sequence and table id generators into mapping XSD ( https://hibernate.atlassian.net/browse/HHH-15989?atlOrigin=eyJpIjoiNTZlYz... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) In-line Hibernate settings for sequence and table id generators, as opposed to a “Map” of config. E.g. {noformat}<xsd:complexType name="sequence-generator"> <!- Standard JPA attributes --> <xsd:attribute name="name" type="xsd:string" use="required"/> <xsd:attribute name="sequence-name" type="xsd:string"/> <xsd:attribute name="catalog" type="xsd:string"/> <xsd:attribute name="schema" type="xsd:string"/> <xsd:attribute name="initial-value" type="xsd:int"/> <xsd:attribute name="allocation-size" type="xsd:int"/>  <xsd:attribute name="per-entity" type="xsd:boolean"/> <xsd:attribute name="per-entity-suffix" type="xsd:string"/> <xsd:attribute name="optizer" type="xsd:string"/> <xsd:attribute name="table-value-column" type="xsd:string"/> </xsd:complexType name="sequence-generator">{noformat} And corresponding annotations: {noformat} /** * For use with the standard {@linkplain TableGenerator @TableGenerator} * providing additional Hibernate configuration of the generator * * @see TableGenerator * @see org.hibernate.id.enhanced.TableGenerator * * @author Steve Ebersole */ @Target({ANNOTATION_TYPE, TYPE, METHOD, FIELD}) @Retention(RUNTIME) @Incubating public @interface TableGeneratorExtension { /** * The name of the associated {@linkplain TableGenerator @TableGenerator}. * * @see TableGenerator#name() */ String name(); /** * Specific type of {@linkplain org.hibernate.id.enhanced.Optimizer optimizer} to use, * if any, to optimize access to the underlying table. * * @see org.hibernate.id.enhanced.OptimizerDescriptor * @see org.hibernate.id.enhanced.StandardOptimizerDescriptor */ String optimizerName() default ""; /** * Hibernate's default is to use a single row for all generators mapped to it, * using {@link org.hibernate.id.enhanced.TableGenerator#DEF_SEGMENT_VALUE} * as the {@link org.hibernate.id.enhanced.TableGenerator#DEF_SEGMENT_COLUMN}. * <p/> * This tells Hibernate to instead use a row for each mapped generator. The * entity name mapped to the generator table * * @see org.hibernate.id.enhanced.TableGenerator#CONFIG_PREFER_SEGMENT_PER_ENTITY * @see AvailableSettings#ID_DB_STRUCTURE_NAMING_STRATEGY */ boolean perEntity() default false; }{noformat} ( https://hibernate.atlassian.net/browse/HHH-15989#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15989#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:674e4eb )

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-15929) Mapping jsonb of different types in a class inheritance hierarchy does not work.

by Thomas Bosch (JIRA)

Thomas Bosch ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c19f84... ) *commented* on HHH-15929 ( https://hibernate.atlassian.net/browse/HHH-15929?atlOrigin=eyJpIjoiNGNkOT... ) Re: Mapping jsonb of different types in a class inheritance hierarchy does not work. ( https://hibernate.atlassian.net/browse/HHH-15929?atlOrigin=eyJpIjoiNGNkOT... ) Same for me. Fixed. Thanks. ( https://hibernate.atlassian.net/browse/HHH-15929#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15929#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:674e4eb )

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-16792) Incorrect generated SQL query when using CriteriaUpdate on an entity with inheritance

by Marco Belladelli (JIRA)

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-16792) Incorrect generated SQL query when using CriteriaUpdate on an entity with inheritance

by Marco Belladelli (JIRA)

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-15989) In-line Hibernate settings for sequence and table id generators into mapping XSD

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15989 ( https://hibernate.atlassian.net/browse/HHH-15989?atlOrigin=eyJpIjoiMmNjNm... ) Re: In-line Hibernate settings for sequence and table id generators into mapping XSD ( https://hibernate.atlassian.net/browse/HHH-15989?atlOrigin=eyJpIjoiMmNjNm... ) The annotations as you posted them look good to me. public @interface TableGeneratorExtension { String name(); String optimizerName() default ""; boolean perEntity() default false; } public @interface SequenceGeneratorExtension { String name(); String optimizerName() default ""; String perEntitySuffix() default "_SEQ"; } How about making name() optional though and resolve the name based on where the annotation is placed? ( https://hibernate.atlassian.net/browse/HHH-15989#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15989#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:674e4eb )

1 year, 6 months

1
0
0 / 0

[JIRA] (HSEARCH-4394) Switch to Jakarta EE as the default standard instead of Java EE

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiYWVhMGUw... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-4394?atlOrigin=eyJpIjoiYWV... ) HSEARCH-4394 ( https://hibernate.atlassian.net/browse/HSEARCH-4394?atlOrigin=eyJpIjoiYWV... ) Switch to Jakarta EE as the default standard instead of Java EE ( https://hibernate.atlassian.net/browse/HSEARCH-4394?atlOrigin=eyJpIjoiYWV... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Before this change: * The main artifacts (no particular suffix, e.g. {{hibernate-search-mapper-orm}}) target Hibernate ORM 5.x + Java EE * There are additional artifacts with a '-jakarta' suffix (e.g. {{hibernate-search-mapper-orm-jakarta}}) to support Hibernate ORM 5.x + Jakarta EE After this change: * The main artifacts (no particular suffix, e.g. {{hibernate-search-mapper-orm}}) target Hibernate ORM 5.x + Jakarta EE * There are additional artifacts with a '-javaee' suffix (e.g. {{hibernate-search-mapper-orm-javaee}}) to support ORM 5.x + Java EE Note we won’t keep those {{-javaee}} artifacts after [https://hibernate.atlassian.net/browse/HSEARCH-4395|https://hibernate.atl...] since ORM 6 does not support Java EE. So ( https://hibernate.atlassian.net/browse/HSEARCH-4394#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4394#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:674e4eb )

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-16866) move enums out of org.hibernate.query.sqm

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=eyJpIjoiYmEwZjA5ZTU1... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16866?atlOrigin=eyJpIjoiYmEwZj... ) HHH-16866 ( https://hibernate.atlassian.net/browse/HHH-16866?atlOrigin=eyJpIjoiYmEwZj... ) move enums out of org.hibernate.query.sqm ( https://hibernate.atlassian.net/browse/HHH-16866?atlOrigin=eyJpIjoiYmEwZj... ) Change By: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Quite a few enums have accumulated in the package {{org.hibernate.query.sqm}}. At least one of them, {{NullOrdering}} , just clearly doesn't belong there. But there are some others which while relevant to the {{sqm}} package have also leaked out onto other API layers including the {{org.hibernate.query.criteria}} package. Since this package is actually some sort of abstraction over {{org.hibernate.query.sqm}}, this is a layer-breaker. Luckily, {{org.hibernate.query.sqm}} is marked {{@Incubating}} so we can move these enums out of there. I’m not quite sure where to move them, however. It might not be a great idea to accumulate too much stuff in {{org.hibernate.query}}. Not sure. ( https://hibernate.atlassian.net/browse/HHH-16866#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16866#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:674e4eb )

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-16866) move enums out of org.hibernate.query.sqm

by Gavin King (JIRA)

1 year, 6 months

1
0
0 / 0

[JIRA] (HHH-16866) move enums out of org.hibernate.query.sqm

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZTI1NjczYTgz... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16866?atlOrigin=eyJpIjoiZTI1Nj... ) HHH-16866 ( https://hibernate.atlassian.net/browse/HHH-16866?atlOrigin=eyJpIjoiZTI1Nj... ) move enums out of org.hibernate.query.sqm ( https://hibernate.atlassian.net/browse/HHH-16866?atlOrigin=eyJpIjoiZTI1Nj... ) Issue Type: Improvement Assignee: Unassigned Components: hibernate-core Created: 28/Jun/2023 07:40 AM Priority: Major Reporter: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Quite a few enums have accumulated in the package org.hibernate.query.sqm. At least one of them, NullOrdering just clearly doesn't belong there. But there are some others which while relevant to the sqm package have also leaked out onto other API layers including the org.hibernate.query.criteria package. Since this package is actually some sort of abstraction over org.hibernate.query.sqm , this is a layer-breaker. Luckily, org.hibernate.query.sqm is marked @Incubating so we can move these enums out of there. I’m not quite sure where to move them, however. It might not be a great idea to accumulate too much stuff in org.hibernate.query. Not sure. ( https://hibernate.atlassian.net/browse/HHH-16866#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16866#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:674e4eb )

1 year, 6 months

1
0
0 / 0

[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=eyJpIjoiNzIzMz... ) Re: max() doesn't work with Enums ( https://hibernate.atlassian.net/browse/HHH-16859?atlOrigin=eyJpIjoiNzIzMz... ) That’s not correct Sir. I pointed out in this issue that there is an inconsistency in enum handling in Hibernate 6. I provided the examples where the automatic conversion is done and those where it isn’t anymore. I also put in the arguments why it might make sense to cover this gap. My intent is not to give the Hibernate Team additional work, just to make the framework better (or at least more user-friendly in that regard). I don't expect or ask you to solve it one way or the other (by introducing new function for explicit type conversion, re-introducing the 5.x behavior or just properly documenting the change), but the current setup will generate more and more confusions as people starts migrating to H6. ( 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