September 2022 - hibernate-issues

[JIRA] (HHH-15548) PostgreSQL: Hibernate creates column with "timestamp with timezone" and then fails to validate it

by Mike Becker (JIRA)

Mike Becker ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6321cb8... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMTczMmI5YWVh... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15548?atlOrigin=eyJpIjoiMTczMm... ) HHH-15548 ( https://hibernate.atlassian.net/browse/HHH-15548?atlOrigin=eyJpIjoiMTczMm... ) PostgreSQL: Hibernate creates column with "timestamp with timezone" and then fails to validate it ( https://hibernate.atlassian.net/browse/HHH-15548?atlOrigin=eyJpIjoiMTczMm... ) Change By: Mike Becker ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6321cb8... ) h2. What was observed? h3. Windows + PostgreSQL 10 or 14 Database / Linux + PostgreSQL 10 Database Hibernate throws the following schema validation exception: {quote}org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: wrong column type encountered in column \[mycolumn] in table \[mytable]; found \[timestamptz (Types#TIMESTAMP)], but expecting \[timestamp(6) with time zone (Types#TIMESTAMP_UTC)]{quote} The underlying Java datatype is java.util.Instant. h2. Additional Information In both databases the {{information_schema}} describes the column as ||data_type||datetime_precision|| |timestamp with time zone|6| The column in the windows database was created with an DDL statement containing {{timestamp(6) with time zone}} as datatype which was extracted from the linux database which had been created by hibernate with {{hibernate.hbm2ddl.auto=create-drop}}. Recent tests showed that the bug also occurs in the linux installation when the application is redeployed. That means, hibernate is rejecting the datatype it created before. h2. What is the Bug? Hibernate states that the “found” datatype would be literally {{timestamptz}}, although postgres itself (via the {{information_schema}}) describes the datatype as {{timestamp with time zone}}. Actually it should not matter, because {{timestamptz}} is just an alias for {{timestamp with time zone}} but it is confusing where Hibernate gets the information from, because it clearly cannot be what the information schema offers. More precisely, the bug is that Hibernate _claims_ the data type would be {{timestamptz}} although it * has been created with {{timestamp(6) with timezone}} * is described by IDEs (e.g. JetBrains Data Grip) as {{timestamp(6) with timezone}} * is described by the information schema as {{timestamp with time zone}} with precision {{6}} * was actually created by hibernate with {{hibernate.hbm2ddl.auto=create-drop}} So we can safely assume, that the datatype *is* actually {{timestamp(6) with timezone}} and therefore, exactly what Hibernate is expecting in the exception text: {{expecting [timestamp(6) with time zone (Types#TIMESTAMP_UTC)]}} Even if hibernate somehow internally recognizes {{timestamp with timezone}} as {{timestamptz}} (which imho is wrong, because Hibernate should use what the information schema says and should not work with its own interpretations), then the data types would still be the same, because {{timestamptz}} is just an alias. ( 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:520255c )

2 years

1
0
0 / 0

[JIRA] (HHH-15548) PostgreSQL: Hibernate creates column with "timestamp with timezone" and then fails to validate it

by Mike Becker (JIRA)

2 years

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=eyJpIjoiMGJhNm... ) 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=eyJpIjoiMGJhNm... ) Updated information about the circumstances under which the error occurs. We can exclude operating system and database version now. ( 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:520255c )

2 years

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... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNWE3OTkwY2Rh... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15548?atlOrigin=eyJpIjoiNWE3OT... ) HHH-15548 ( https://hibernate.atlassian.net/browse/HHH-15548?atlOrigin=eyJpIjoiNWE3OT... ) 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=eyJpIjoiNWE3OT... ) Change By: Mike Becker ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6321cb8... ) h2. What was observed? h3. Windows + PostgreSQL 10 or 14 Database / Linux + PostgreSQL 10 Database Hibernate throws the following schema validation exception: {quote}org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: wrong column type encountered in column \[mycolumn] in table \[mytable]; found \[timestamptz (Types#TIMESTAMP)], but expecting \[timestamp(6) with time zone (Types#TIMESTAMP_UTC)]{quote} The underlying Java datatype is java.util.Instant. h3. Linux + PostgreSQL 10 Database The exception is not thrown. h2. Additional Information In both databases the {{information_schema}} describes the column as ||data_type||datetime_precision|| |timestamp with time zone|6| The column in the windows database was created with an DDL statement containing {{timestamp(6) with time zone}} as datatype which was extracted from the linux database which had been created by hibernate with {{hibernate.hbm2ddl.auto=create-drop}}. Recent tests showed that the bug also occurs in the linux installation when the application is redeployed. That means, hibernate is rejecting the datatype it created before. h2. What is the Bug? Hibernate states that the “found” datatype would be literally {{timestamptz}}, although postgres itself (via the {{information_schema}}) describes the datatype as {{timestamp with time zone}}. Actually it should not matter, because {{timestamptz}} is just an alias for {{timestamp with time zone}} but it is confusing where Hibernate gets the information from, because it clearly cannot be what the information schema offers. More precisely, the bug is that Hibernate _claims_ the data type would be {{timestamptz}} although it * has been created with {{timestamp(6) with timezone}} * is described by IDEs (e.g. JetBrains Data Grip) as {{timestamp(6) with timezone}} * is described by the information schema as {{timestamp with time zone}} with precision {{6}} So we can safely assume, that the datatype *is* actually {{timestamp(6) with timezone}} and therefore, exactly what Hibernate is expecting in the exception text: {{expecting [timestamp(6) with time zone (Types#TIMESTAMP_UTC)]}} Even if hibernate somehow internally recognizes {{timestamp with timezone}} as {{timestamptz}} (which imho is wrong, because Hibernate should use what the information schema says and should not work with its own interpretations), then the data types would still be the same, because {{timestamptz}} is just an alias. ( 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:520255c )

2 years

1
0
0 / 0

[JIRA] (HHH-15045) onFlushDirty() invoked on parent entity in a @OneToOne relationship when no table columns are changed

by Sanne Grinovero (JIRA)

2 years

1
0
0 / 0

[JIRA] (HHH-15235) PropertyAccessException on OneToOne mapping after migration to Hibernate 5.6

by Sanne Grinovero (JIRA)

2 years

1
0
0 / 0

[JIRA] (HHH-15555) Remove use of @AutomaticFeature in GraalVM module

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiM2IwNWFjZmI3... ) / Task ( https://hibernate.atlassian.net/browse/HHH-15555?atlOrigin=eyJpIjoiM2IwNW... ) HHH-15555 ( https://hibernate.atlassian.net/browse/HHH-15555?atlOrigin=eyJpIjoiM2IwNW... ) Remove use of @AutomaticFeature in GraalVM module ( https://hibernate.atlassian.net/browse/HHH-15555?atlOrigin=eyJpIjoiM2IwNW... ) Change By: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The annotation {{ com.oracle.svm.core.annotate.AutomaticFeature }} is deprecated, and the GraalVM team recommends not enabling such features automatically, but rather have the user opt-in explicitly, or list the feature among the native-image parameters in the metadata. This also serves to align with what we already did in ORM 6 via [https://hibernate.atlassian.net/browse/HHH-15484|https://hibernate.atlass...] : as the graal-sdk doesn’t expose this annotation. However this is not a backport of [https://hibernate.atlassian.net/browse/HHH-15484|https://hibernate.atlass...] , as the new API is not compatible with JDK8. We will still rely on the existing svm artifact to compile our hibernate-graalvm extension, but we’ll do so expecting it to be replaced by the graal-sdk artifact at runtime - so this needs a little care to be runtime compatible with both libraries to allow for the transition. ( https://hibernate.atlassian.net/browse/HHH-15555#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15555#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:520255c )

2 years

1
0
0 / 0

[JIRA] (HHH-15555) Remove use of @AutomaticFeature in GraalVM module

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNDJjZWUyYTRj... ) / Task ( https://hibernate.atlassian.net/browse/HHH-15555?atlOrigin=eyJpIjoiNDJjZW... ) HHH-15555 ( https://hibernate.atlassian.net/browse/HHH-15555?atlOrigin=eyJpIjoiNDJjZW... ) Remove use of @AutomaticFeature in GraalVM module ( https://hibernate.atlassian.net/browse/HHH-15555?atlOrigin=eyJpIjoiNDJjZW... ) Change By: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The annotation com.oracle.svm.core.annotate.AutomaticFeature is deprecated, and the GraalVM team recommends not enabling such features automatically, but rather have the user opt-in explicitly, or list the feature among the native-image parameters in the metadata. This also serves to align with what we already did in ORM 6 via [https://hibernate.atlassian.net/browse/HHH-15484|https://hibernate.atlass...] : as the graal-sdk doesn’t expose this annotation. However t his this is not a backport of [https://hibernate.atlassian.net/browse/HHH-15484|https://hibernate.atlass...] , as the new API is not compatible with JDK8. We will still rely on the existing svm artifact to compile our hibernate-graalvm extension, but we’ll do so expecting it to be replaced by the graal-sdk artifact at runtime - so this needs a little care to be runtime compatible with both libraries to allow for the transition. ( https://hibernate.atlassian.net/browse/HHH-15555#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15555#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:520255c )

2 years

1
0
0 / 0

[JIRA] (HHH-15555) Remove use of @AutomaticFeature in GraalVM module

by Sanne Grinovero (JIRA)

2 years

1
0
0 / 0

[JIRA] (HHH-15555) Remove use of @AutomaticFeature in GraalVM module

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZmZkOWJjY2Iw... ) / Task ( https://hibernate.atlassian.net/browse/HHH-15555?atlOrigin=eyJpIjoiZmZkOW... ) HHH-15555 ( https://hibernate.atlassian.net/browse/HHH-15555?atlOrigin=eyJpIjoiZmZkOW... ) Remove use of @AutomaticFeature in GraalVM module ( https://hibernate.atlassian.net/browse/HHH-15555?atlOrigin=eyJpIjoiZmZkOW... ) Issue Type: Task Assignee: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Created: 27/Sep/2022 02:22 AM Priority: Major Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The annotation com.oracle.svm.core.annotate.AutomaticFeature is deprecated, and the GraalVM team recommends not enabling such features automatically, but rather have the user opt-in explicitly, or list the feature among the native-image parameters in the metadata. This also serves to align with what we already did in ORM 6 via https://hibernate.atlassian.net/browse/HHH-15484 ( https://hibernate.atlassian.net/browse/HHH-15484 ) : as the graal-sdk doesn’t expose this annotation. However t his is not a backport of https://hibernate.atlassian.net/browse/HHH-15484 ( https://hibernate.atlassian.net/browse/HHH-15484 ) , as the new API is not compatible with JDK8. We will still rely on the existing svm artifact to compile our hibernate-graalvm extension, but we’ll do so expecting it to be replaced by the graal-sdk artifact at runtime - so this needs a little care to be runtime compatible with both libraries to allow for the transition. ( https://hibernate.atlassian.net/browse/HHH-15555#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15555#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:520255c )

2 years

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