September 2022 - hibernate-issues

[JIRA] (HHH-15549) incorrect DDL mapping DECIMAL -> BOOLEAN on Oracle

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=eyJpIjoiODU1YmZjNGVh... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15549?atlOrigin=eyJpIjoiODU1Ym... ) HHH-15549 ( https://hibernate.atlassian.net/browse/HHH-15549?atlOrigin=eyJpIjoiODU1Ym... ) incorrect DDL mapping DECIMAL -> BOOLEAN on Oracle ( https://hibernate.atlassian.net/browse/HHH-15549?atlOrigin=eyJpIjoiODU1Ym... ) Change By: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I just stumbled on this buried treasure in {{OracleDialect}}: {code:java} case Types.DECIMAL: if ( scale == 0 ) { switch ( precision ) { case 1: return jdbcTypeRegistry.getDescriptor( Types.BOOLEAN );{code} Of course, {{precision==1}} means one _decimal_ digit of precision, not one bit. UPDATE: So, OK, this is for reverse engineering I guess, but it still seems pretty wrong to assume that every {{NUMBER(1,0)}} is a boolean value and not a one - digit decimal. ( https://hibernate.atlassian.net/browse/HHH-15549#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15549#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#100207- sha1:1c92a42 )

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15549) incorrect DDL mapping DECIMAL -> BOOLEAN on Oracle

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=eyJpIjoiYjQzZjU5OWQ1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15549?atlOrigin=eyJpIjoiYjQzZj... ) HHH-15549 ( https://hibernate.atlassian.net/browse/HHH-15549?atlOrigin=eyJpIjoiYjQzZj... ) incorrect DDL mapping DECIMAL -> BOOLEAN on Oracle ( https://hibernate.atlassian.net/browse/HHH-15549?atlOrigin=eyJpIjoiYjQzZj... ) Change By: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I just stumbled on this buried treasure in {{OracleDialect}}: {code:java} case Types.DECIMAL: if ( scale == 0 ) { switch ( precision ) { case 1: return jdbcTypeRegistry.getDescriptor( Types.BOOLEAN );{code} Of course, {{precision==1}} means one _decimal_ digit of precision, not one bit. Now UPDATE: So , _just by pure luck OK , _ this doesn’t break anything because in Oracle pre-23c is for reverse engineering I guess , we map {{BOOLEAN}} but it still seems pretty wrong to assume that every {{ number NUMBER (1,0)}} , but by the same token that whole block of code looks just completely pointless is a boolean value and not a one digit decimal. I believe it should be deleted. ( https://hibernate.atlassian.net/browse/HHH-15549#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15549#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#100207- sha1:1c92a42 )

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15545) @NotFound(Ignore) defaults to eager loading

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15545 ( https://hibernate.atlassian.net/browse/HHH-15545?atlOrigin=eyJpIjoiOGRlYT... ) Re: @NotFound(Ignore) defaults to eager loading ( https://hibernate.atlassian.net/browse/HHH-15545?atlOrigin=eyJpIjoiOGRlYT... ) Well it turns out you’re incredibly blessed that I was bored this morning, and I fixed all the miscellaneous issues with this here: https://github.com/hibernate/hibernate-orm/pull/5344 ( https://github.com/hibernate/hibernate-orm/pull/5344 ) ( https://hibernate.atlassian.net/browse/HHH-15545#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15545#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#100207- sha1:1c92a42 )

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15549) incorrect DDL mapping DECIMAL -> BOOLEAN on Oracle

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=eyJpIjoiZWYyYWY5MmM4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15549?atlOrigin=eyJpIjoiZWYyYW... ) HHH-15549 ( https://hibernate.atlassian.net/browse/HHH-15549?atlOrigin=eyJpIjoiZWYyYW... ) incorrect DDL mapping DECIMAL -> BOOLEAN on Oracle ( https://hibernate.atlassian.net/browse/HHH-15549?atlOrigin=eyJpIjoiZWYyYW... ) Issue Type: Bug Affects Versions: 6.1.3 Assignee: Unassigned Created: 26/Sep/2022 04:43 AM Priority: Major Reporter: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I just stumbled on this buried treasure in OracleDialect : case Types.DECIMAL: if ( scale == 0 ) { switch ( precision ) { case 1: return jdbcTypeRegistry.getDescriptor( Types.BOOLEAN ); Of course, precision==1 means one decimal digit of precision, not one bit. Now, just by pure luck, this doesn’t break anything because in Oracle pre-23c, we map BOOLEAN to number(1,0) , but by the same token that whole block of code looks just completely pointless. I believe it should be deleted. ( https://hibernate.atlassian.net/browse/HHH-15549#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15549#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#100207- sha1:1c92a42 )

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15545) @NotFound(Ignore) defaults to eager loading

by Manuel O (JIRA)

Manuel O ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) *commented* on HHH-15545 ( https://hibernate.atlassian.net/browse/HHH-15545?atlOrigin=eyJpIjoiN2M5Nj... ) Re: @NotFound(Ignore) defaults to eager loading ( https://hibernate.atlassian.net/browse/HHH-15545?atlOrigin=eyJpIjoiN2M5Nj... ) Thanks - that’s also my impression about this. So a lazy collection should never be annotated with NotFound, shouldn’t it!? I think there was already a proposal to have warning when adding a NotFound on a lazy collection!? ( https://hibernate.atlassian.net/browse/HHH-15545#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15545#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#100207- sha1:1c92a42 )

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15529) Cannot override non-identifier propety from @MappedSuperclass and make it identifier in subclass

by JohannesMartin (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15529) Cannot override non-identifier propety from @MappedSuperclass and make it identifier in subclass

by JohannesMartin (JIRA)

JohannesMartin ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMDcxYzUyNTdi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15529?atlOrigin=eyJpIjoiMDcxYz... ) HHH-15529 ( https://hibernate.atlassian.net/browse/HHH-15529?atlOrigin=eyJpIjoiMDcxYz... ) Cannot override non-identifier propety from @MappedSuperclass and make it identifier in subclass ( https://hibernate.atlassian.net/browse/HHH-15529?atlOrigin=eyJpIjoiMDcxYz... ) Change By: JohannesMartin ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I’ve got a @MappedSuperClass A defining field testA as non-identifier. Class B extends Class A, defining additional field testB. Class B annotates both field testA and field testB with @Id. At runtime, hibernate 5.6.11 complains: org.hibernate.MappingException: You cannot override the \[testA] non-identifier property from the \[sample.entities.A] base class or @MappedSuperclass and make it an identifier in the \[sample.entities.B] subclass\! Earlier versions just silently ignore the @Id annotation on testA. If I annotate testA as @Id in the MappedSuperclass, the code runs fine, but this violates JPA spec (JPA 2.1 [http://download.oracle.com/otndocs/jcp/persistence-2_1-fr-eval-spec|http:... Chapter 2.4): {quote}The primary key must be defined on the entity class that is the root of the entity hierarchy or on a mapped superclass that is a (direct or indirect) superclass of all entity classes in the entity hierarchy. The primary key must be defined exactly once in an entity hierarchy.{quote} Why does hibernate handle things like this? Is there a way around it. ? ( https://hibernate.atlassian.net/browse/HHH-15529#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15529#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#100207- sha1:1c92a42 )

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15545) @NotFound(Ignore) defaults to eager loading

by Gavin King (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15509) Avoid entity loading on delete() when possible

by Gavin King (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15548) PostgreSQL: Hibernate claims to have found "timestamptz" and also claims that it is incompatible with "timestamp with timezone"

by Mike Becker (JIRA)

Mike Becker ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6321cb8... ) *commented* on HHH-15548 ( https://hibernate.atlassian.net/browse/HHH-15548?atlOrigin=eyJpIjoiOGRiZj... ) Re: PostgreSQL: Hibernate claims to have found "timestamptz" and also claims that it is incompatible with "timestamp with timezone" ( https://hibernate.atlassian.net/browse/HHH-15548?atlOrigin=eyJpIjoiOGRiZj... ) Updated the information on how the columns were created in each database to be more precise. ( https://hibernate.atlassian.net/browse/HHH-15548#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15548#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#100207- sha1:1c92a42 )

2 years, 2 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 September 2022