November 2022 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-13559) Add support for on-delete="cascade" support to unidirectional *ToOne relationships for Sybase

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13559 ( https://hibernate.atlassian.net/browse/HHH-13559?atlOrigin=eyJpIjoiYTUzZj... ) Re: Add support for on-delete="cascade" support to unidirectional *ToOne relationships for Sybase ( https://hibernate.atlassian.net/browse/HHH-13559?atlOrigin=eyJpIjoiYTUzZj... ) We should close this issue. Sybase doesn’t support on delete and I doubt it’s worth going to the effort of having schema export create triggers to emulate it! ( https://hibernate.atlassian.net/browse/HHH-13559#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13559#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#100210- sha1:eab5823 )

1 year, 5 months

1
0
0 / 0

[JIRA] (HHH-15762) prefer including unique constraints in 'create table' instead of using 'alter table'

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15762 ( https://hibernate.atlassian.net/browse/HHH-15762?atlOrigin=eyJpIjoiYTdjYW... ) Re: prefer including unique constraints in 'create table' instead of using 'alter table' ( https://hibernate.atlassian.net/browse/HHH-15762?atlOrigin=eyJpIjoiYTdjYW... ) As a second part of this work, I’ve made sure that unique constraints on nullable columns have a consistent semantic across databases including DB2 and SQL Server. When the unique key includes a nullable column, we now generate: create unique nonclustered index name on table (column) where column is not null on SQL Server (after 2008). And on DB2 (after 10.5) it is either: create unique index name on table (column) exclude null keys or, on i or Z series: create unique where not null index name on table (column) As an aside I have no clue when the where not null syntax was introduced, which is an issue for the community dialects. Now, the bad guy is Sybase. There’s still no way to do this on Sybase, since Sybase is essentially unmaintained. My solution is, for maximum portability, simply ignore unique constraints involving nullable columns on Sybase. I realize this is a debatable decision, but I think it’s the best and most consistent option. ( https://hibernate.atlassian.net/browse/HHH-15762#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15762#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#100210- sha1:eab5823 )

1 year, 5 months

1
0
0 / 0

[JIRA] (HHH-15767) missing unique constraints from optional @OneToOne

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15767 ( https://hibernate.atlassian.net/browse/HHH-15767?atlOrigin=eyJpIjoiYWIzNm... ) Re: missing unique constraints from optional @OneToOne ( https://hibernate.atlassian.net/browse/HHH-15767?atlOrigin=eyJpIjoiYWIzNm... ) So I now sort of understand why this was like that. Essentially: we just didn’t have consistent semantics for our unique constraints, since on Sybase, SQL Server, and DB2 the traditional semantics was that null=null for deciding uniqueness. And that wasn’t what we wanted for a @OneToOne with a FK. Well, as of 2022, that’s been semi-fixed for a while in SQL Server and DB2. There is a way to create a unique index where null<>null on SQL server and on all flavors of DB2. For SQL server it is create unique nonclustered index name on table (column) where column is not null And on DB2 it is either: create unique index name on table (column) exclude null keys or, on i or Z series: create unique where not null index name on table (column) The only database where it’s still impossible is Sybase. So my solution is, as kind of a second part of https://hibernate.atlassian.net/browse/HHH-15762 ( https://hibernate.atlassian.net/browse/HHH-15762 ) , finally give our unique constraints on nullable columns a consistent semantic, and just refuse to create them on Sybase. ( https://hibernate.atlassian.net/browse/HHH-15767#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15767#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#100210- sha1:eab5823 )

1 year, 5 months

1
0
0 / 0

[JIRA] (HHH-15770) allow @OnDelete to specify RESTRICT, SET_NULL, SET_DEFAULT

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15770 ( https://hibernate.atlassian.net/browse/HHH-15770?atlOrigin=eyJpIjoiYzhhYW... ) Re: allow @OnDelete to specify RESTRICT, SET_NULL, SET_DEFAULT ( https://hibernate.atlassian.net/browse/HHH-15770?atlOrigin=eyJpIjoiYzhhYW... ) Also let you specify @ColumnDefault for an association, since that works nicely with SET_NULL. ( https://hibernate.atlassian.net/browse/HHH-15770#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15770#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#100210- sha1:eab5823 )

1 year, 5 months

1
0
0 / 0

[JIRA] (HHH-15770) allow @OnDelete to specify RESTRICT, SET_NULL, SET_DEFAULT

by Gavin King (JIRA)

1 year, 5 months

1
0
0 / 0

[JIRA] (HHH-15770) allow @OnDelete to specify RESTRICT, SET_NULL, SET_DEFAULT

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=eyJpIjoiOTQyYWM4ZjY4... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15770?atlOrigin=eyJpIjoiOTQyYW... ) HHH-15770 ( https://hibernate.atlassian.net/browse/HHH-15770?atlOrigin=eyJpIjoiOTQyYW... ) allow @OnDelete to specify RESTRICT, SET_NULL, SET_DEFAULT ( https://hibernate.atlassian.net/browse/HHH-15770?atlOrigin=eyJpIjoiOTQyYW... ) Issue Type: Improvement Assignee: Unassigned Components: hibernate-core Created: 27/Nov/2022 00:39 AM Priority: Major Reporter: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We have a whole OnDeleteAction with just two enumerated values, so we may as add RESTRICT , SET_NULL , SET_DEFAULT to the list of options. ( https://hibernate.atlassian.net/browse/HHH-15770#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15770#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#100210- sha1:eab5823 )

1 year, 5 months

1
0
0 / 0

[JIRA] (HHH-15769) validation @NotNull does not mark Column as null

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15769 ( https://hibernate.atlassian.net/browse/HHH-15769?atlOrigin=eyJpIjoiYzVkNj... ) Re: validation @NotNull does not mark Column as null ( https://hibernate.atlassian.net/browse/HHH-15769?atlOrigin=eyJpIjoiYzVkNj... ) Actually I think I was mistaken. One of the tests was sort-of implicitly making the assumption that this works for subclasses in single table inheritance when of course it doesn’t. I believe this can be closed. ( https://hibernate.atlassian.net/browse/HHH-15769#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15769#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#100210- sha1:eab5823 )

1 year, 5 months

1
0
0 / 0

[JIRA] (HHH-15769) validation @NotNull does not mark Column as null

by Gavin King (JIRA)

1 year, 5 months

1
0
0 / 0

[JIRA] (HHH-15768) incorrect deprecation warning being logged: HHH90000021: Encountered deprecated setting [javax.persistence.sharedCache.mode], use [jakarta.persistence.sharedCache.mode] instead

by JB Nizet (JIRA)

JB Nizet ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZWM2MDIwZDQ1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15768?atlOrigin=eyJpIjoiZWM2MD... ) HHH-15768 ( https://hibernate.atlassian.net/browse/HHH-15768?atlOrigin=eyJpIjoiZWM2MD... ) incorrect deprecation warning being logged: HHH90000021: Encountered deprecated setting [javax.persistence.sharedCache.mode], use [jakarta.persistence.sharedCache.mode] instead ( https://hibernate.atlassian.net/browse/HHH-15768?atlOrigin=eyJpIjoiZWM2MD... ) Change By: JB Nizet ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The following warning message is being logged when starting an application (with a basic Spring Boot 3 application, but I don’t think it matters): HHH90000021: Encountered deprecated setting [javax.persistence.sharedCache.mode], use [jakarta.persistence.sharedCache.mode] instead But this setting has never been explicitly set anywahere anywhere. I’ve tracked down the place where this warning is logged. It’s in MetadataBuilderImpl, line 626: [https://github.com/hibernate/hibernate-orm/blob/main/hibernate-core/src/m...] Analyzing the code, it gets a setting, specifies a default value in case the setting has not been set, which is SharedCacheMode.UNSPECIFIED, and then, when getting this default value, logs a warning saying that this this value is deprecated. ( https://hibernate.atlassian.net/browse/HHH-15768#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15768#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#100210- sha1:eab5823 )

1 year, 5 months

1
0
0 / 0

[JIRA] (HHH-15768) incorrect deprecation warning being logged: HHH90000021: Encountered deprecated setting [javax.persistence.sharedCache.mode], use [jakarta.persistence.sharedCache.mode] instead

by JB Nizet (JIRA)

JB Nizet ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYTkyZGVjZjBl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15768?atlOrigin=eyJpIjoiYTkyZG... ) HHH-15768 ( https://hibernate.atlassian.net/browse/HHH-15768?atlOrigin=eyJpIjoiYTkyZG... ) incorrect deprecation warning being logged: HHH90000021: Encountered deprecated setting [javax.persistence.sharedCache.mode], use [jakarta.persistence.sharedCache.mode] instead ( https://hibernate.atlassian.net/browse/HHH-15768?atlOrigin=eyJpIjoiYTkyZG... ) Issue Type: Bug Affects Versions: 6.1.5 Assignee: Unassigned Components: hibernate-core Created: 26/Nov/2022 07:18 AM Priority: Minor Reporter: JB Nizet ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The following warning message is being logged when starting an application (with a basic Spring Boot 3 application, but I don’t think it matters): HHH90000021: Encountered deprecated setting [javax.persistence.sharedCache.mode] , use [jakarta.persistence.sharedCache.mode] instead But this setting has never been explicitly set anywahere. I’ve tracked down the place where this warning is logged. It’s in MetadataBuilderImpl, line 626: https://github.com/hibernate/hibernate-orm/blob/main/hibernate-core/src/m... ( https://github.com/hibernate/hibernate-orm/blob/main/hibernate-core/src/m... ) Analyzing the code, it gets a setting, specifies a default value in case the setting has not been set, which is SharedCacheMode.UNSPECIFIED, and then, when getting this default value, logs a warning saying that this this value is deprecated. ( https://hibernate.atlassian.net/browse/HHH-15768#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15768#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#100210- sha1:eab5823 )

1 year, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2022