March 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-4823) Clarify the documentation of the configuration property about the Elasticsearch version

by Yoann Rodière (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-16352) DynamicUpdate and Statement/jdbc batch size leads to wrong parameter binding exception

by Jan Schatteman (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-16317) InstantAsTimestampWithTimeZoneJdbcType doesn't work for timestamp on PG-JDBC

by Christian Beikov (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-16317) InstantAsTimestampWithTimeZoneJdbcType doesn't work for timestamp on PG-JDBC

by Christian Beikov (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-16317) InstantAsTimestampWithTimeZoneJdbcType doesn't work for timestamp on PostgreSQL

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzVkMDkzOWFh... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16317?atlOrigin=eyJpIjoiMzVkMD... ) HHH-16317 ( https://hibernate.atlassian.net/browse/HHH-16317?atlOrigin=eyJpIjoiMzVkMD... ) InstantAsTimestampWithTimeZoneJdbcType doesn't work for timestamp on PostgreSQL ( https://hibernate.atlassian.net/browse/HHH-16317?atlOrigin=eyJpIjoiMzVkMD... ) Change By: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) This There is useful when one wants to bind a {{timestamp}} parameter pg-jdbc issue that prevents us from using this type: [https://github.com/pgjdbc/pgjdbc/issues/2862|https://github.com/pgjdbc/pg...] Binding to an {{ Instant timestamptz }}, which might fail on PostgreSQL, because right now, we use {{InstantAsTimestampWithTimeZoneJdbcType}} is our default choice for that dialect, which binds {{ OffsetDateTime Instant }} through the JDBC driver. It has yet to be confirmed if this is a bug or not , works without problems, but pgjdbc shifts {{OffsetDateTime}} to the JVM TZ when binding to a {{timestamp}} column. If we can’t be sure that this type is correct JDBC behavior, we might as well drop the {{InstantAsTimestampWithTimeZoneJdbcType}} and use {{InstantAsTimestampJdbcType}} instead for PostgreSQL used. NB: Using the default {{ InstantAsTimestampJdbcType TimestampUtcAsJdbcTimestampJdbcType }} uses a shared calendar for passing UTC on the other hand will work perfectly fine, as that will always pass the time zone as argument. Maybe we need to copy that to be safe, but we could switch between a copying and shared implementation based on what we know about the drivers. ( https://hibernate.atlassian.net/browse/HHH-16317#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16317#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#100219- sha1:eb3f1fe )

3 years

1
0
0 / 0

[JIRA] (HHH-16317) InstantAsTimestampWithTimeZoneJdbcType doesn't work for timestamp on PostgreSQL

by Christian Beikov (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-15874) Can't access override property in sub-class when use kotlin data class

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15874 ( https://hibernate.atlassian.net/browse/HHH-15874?atlOrigin=eyJpIjoiZGZkY2... ) Re: Can't access override property in sub-class when use kotlin data class ( https://hibernate.atlassian.net/browse/HHH-15874?atlOrigin=eyJpIjoiZGZkY2... ) By using @get: you are telling the Kotlin Compiler to put the annotations on the Getter it generates for the data class property instead of the field. Since Kotlin duplicates fields, using field annotations is actually not a good idea. It’s so strange, Kotlin prefers to model properties through getters/setters but still puts annotations on the field. This simply is a recipe for disaster. Anyway, I don’t know what changed in Hibernate 6 that changed the behavior, but we will look into this when we can. ( https://hibernate.atlassian.net/browse/HHH-15874#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15874#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#100219- sha1:eb3f1fe )

3 years

1
0
0 / 0

[JIRA] (HHH-16358) TABLE_PER_CLASS one-to-many fails to persist

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=eyJpIjoiYjdmMTc3Mjk3... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16358?atlOrigin=eyJpIjoiYjdmMT... ) HHH-16358 ( https://hibernate.atlassian.net/browse/HHH-16358?atlOrigin=eyJpIjoiYjdmMT... ) TABLE_PER_CLASS one-to-many fails to persist ( https://hibernate.atlassian.net/browse/HHH-16358?atlOrigin=eyJpIjoiYjdmMT... ) Issue Type: Bug Affects Versions: 6.2.0.CR4 Assignee: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: hibernate-core Created: 22/Mar/2023 11:32 AM Fix Versions: 6.2.0 Priority: Major Reporter: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) @Entity @Table(name = "table_per_class_base" ) @Inheritance(strategy = InheritanceType.TABLE_PER_CLASS) public abstract class TablePerClassBase { TablePerClassEmbeddable embeddable; } @Embeddable public class TablePerClassEmbeddable { @OneToMany @JoinColumn(name = "embeddableParent" ) Set<TablePerClassBase> children; } @Entity @Table(name = "table_per_class_sub_1" ) public class TablePerClassSub1 extends TablePerClassBase {} @Entity @Table(name = "table_per_class_sub_2" ) public class TablePerClassSub2 extends TablePerClassBase {} Roughly this model fails to persist elements. An assertion in OneToManyPersister#buildTableUpdate seems to be too strict or maybe even wrong. assert tableReference.getTableName().equals( elementType.getIdentifierMapping().getContainingTableExpression() ) I think it should rather be assert elementType.containsTableReference(tableReference.getTableName()) ( https://hibernate.atlassian.net/browse/HHH-16358#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16358#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#100219- sha1:eb3f1fe )

3 years

1
0
0 / 0

[JIRA] (HHH-16348) Re-add JdbcOperationQuery#getAppliedParameters for query extensions

by Christian Beikov (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-16333) Handle converters properly in BasicPluralType

by Christian Beikov (JIRA)

3 years

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 March 2023