July 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16943) Column ordering leads to wrong column order in unique constraints

by Benedikt Waldvogel (JIRA)

Benedikt Waldvogel ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMTM1Y2ZlOGY1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16943?atlOrigin=eyJpIjoiMTM1Y2... ) HHH-16943 ( https://hibernate.atlassian.net/browse/HHH-16943?atlOrigin=eyJpIjoiMTM1Y2... ) Column ordering leads to wrong column order in unique constraints ( https://hibernate.atlassian.net/browse/HHH-16943?atlOrigin=eyJpIjoiMTM1Y2... ) Change By: Benedikt Waldvogel ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) h3. Given {code:java}@Entity @Table(uniqueConstraints = @UniqueConstraint(name = "uk_b_a", columnNames = { "b", "a" })) class TestEntity { @Id private Long id; private String b; private String a; }{code} Note that we define an explicit unique constraint on the columns *(b, a)* (in that very order). The column order could be important since the underlying unique index should be used to speed-up queries that select all entities for a given value of “b”. h3. Actual vs. Expected When the schema gets created in the context of a JPA EntityManagerFactory, the columns are (re-)ordered during construction of the [SessionFactoryImpl, Line 252: bootMetamodel.orderColumns( false )|https://github.com/hibernate/hibernate-orm/blob/58aff00957721074a4a3937256edd64a067bc943/hibernate-core/src/main/java/org/hibernate/internal/SessionFactoryImpl.java#L252] This leads to the following DDL: {code:sql}create table "TestEntity" ( id bigint not null, a varchar(255), b varchar(255), primary key (id), constraint uk_b_a unique (a, b) );{code} Note that “uk_b_a” is created with columns {color:#bf2600}*(a, b)*{color} instead of the expected column order *(b, a)*. h3. Workaround One can restore the behavior of Hibernate 6.1 by switching to the legacy column ordering strategy via {{hibernate.column_ordering_strategy=legacy}}. h3. Test Case _Upcoming [https : I’ll submit a PR with a unit test for this issue //github. _ com/hibernate/hibernate-orm/pull/7007|https://github.com/hibernate/hibern...] ( https://hibernate.atlassian.net/browse/HHH-16943#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16943#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#100232- sha1:33a7c72 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16944) Enable JSON aggregate constraints on Oracle

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZmM2ZGYwMDNj... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16944?atlOrigin=eyJpIjoiZmM2ZG... ) HHH-16944 ( https://hibernate.atlassian.net/browse/HHH-16944?atlOrigin=eyJpIjoiZmM2ZG... ) Enable JSON aggregate constraints on Oracle ( https://hibernate.atlassian.net/browse/HHH-16944?atlOrigin=eyJpIjoiZmM2ZG... ) Issue Type: Improvement Assignee: Unassigned Created: 17/Jul/2023 01:33 AM Priority: Major Reporter: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We only have check constraints enabled for 23c right now, but we could also enable them for earlier versions if we used the json_value syntax instead of the dot syntax. Note that the dot syntax is only supported in SELECT and WHERE clauses according to Loic from Oracle. ( https://hibernate.atlassian.net/browse/HHH-16944#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16944#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#100232- sha1:33a7c72 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HBX-2547) Review the use of method IConfiguration#addClass(IPersistentClass)

by Koen Aers (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16942) OneToOne Mapping with PartitionKey fails

by Christian Beikov (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16942) OneToOne Mapping with PartitionKey fails

by Christian Beikov (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16943) Column ordering leads to wrong column order in unique constraints

by Benedikt Waldvogel (JIRA)

Benedikt Waldvogel ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOTkwNGM4NmNj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16943?atlOrigin=eyJpIjoiOTkwNG... ) HHH-16943 ( https://hibernate.atlassian.net/browse/HHH-16943?atlOrigin=eyJpIjoiOTkwNG... ) Column ordering leads to wrong column order in unique constraints ( https://hibernate.atlassian.net/browse/HHH-16943?atlOrigin=eyJpIjoiOTkwNG... ) Issue Type: Bug Affects Versions: 6.2.6 Assignee: Unassigned Components: hibernate-core Created: 17/Jul/2023 01:14 AM Priority: Major Reporter: Benedikt Waldvogel ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Given ----- @Entity @Table(uniqueConstraints = @UniqueConstraint(name = "uk_b_a" , columnNames = { "b" , "a" })) class TestEntity { @Id private Long id; private String b; private String a; } Note that we define an explicit unique constraint on the columns *(b, a)* (in that very order). The column order could be important since the underlying unique index should be used to speed-up queries that select all entities for a given value of “b”. Actual vs. Expected ------------------- When the schema gets created in the context of a JPA EntityManagerFactory, the columns are (re-)ordered during construction of the SessionFactoryImpl, Line 252: bootMetamodel.orderColumns( false ) ( https://github.com/hibernate/hibernate-orm/blob/58aff00957721074a4a393725... ) This leads to the following DDL: create table "TestEntity" ( id bigint not null , a varchar (255), b varchar (255), primary key (id), constraint uk_b_a unique ( a , b) ); Note that “uk_b_a” is created with columns *(a, b)* instead of the expected column order *(b, a)*. Workaround ---------- One can restore the behavior of Hibernate 6.1 by switching to the legacy column ordering strategy via hibernate.column_ordering_strategy=legacy. Test Case --------- Upcoming: I’ll submit a PR with a unit test for this issue. ( https://hibernate.atlassian.net/browse/HHH-16943#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16943#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#100232- sha1:33a7c72 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16901) Hibernate 6 : Embedded field not correctly instantiated

by Marco Belladelli (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16888) Left join with exists subquery adds extra join

by Marco Belladelli (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16860) OneToMany with inherited classes on both sides

by Marco Belladelli (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HSEARCH-4891) Upgrade JBeret to 2.1.2.Final

by Marko Bekhta (JIRA)

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