September 2022 - hibernate-issues

[JIRA] (HHH-11757) Add support for OFFSET clause for DB2 version 12+

by lbruun (JIRA)

lbruun ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c95f4c... ) *commented* on HHH-11757 ( https://hibernate.atlassian.net/browse/HHH-11757?atlOrigin=eyJpIjoiMWFlMG... ) Re: Add support for OFFSET clause for DB2 version 12+ ( https://hibernate.atlassian.net/browse/HHH-11757?atlOrigin=eyJpIjoiMWFlMG... ) I think this was fixed in https://hibernate.atlassian.net/browse/HHH-15042 ( https://hibernate.atlassian.net/browse/HHH-15042 ) ? ( https://hibernate.atlassian.net/browse/HHH-11757#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-11757#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#100206- sha1:3ac329d )

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-15475) Db2 now support lock timeout (as of v11.5.6)

by lbruun (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-15475) Db2 now support lock timeout (as of v11.5.6)

by lbruun (JIRA)

lbruun ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c95f4c... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiODFiNWRjZTc0... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15475?atlOrigin=eyJpIjoiODFiNW... ) HHH-15475 ( https://hibernate.atlassian.net/browse/HHH-15475?atlOrigin=eyJpIjoiODFiNW... ) Db2 now support lock timeout (as of v11.5.6) ( https://hibernate.atlassian.net/browse/HHH-15475?atlOrigin=eyJpIjoiODFiNW... ) Change By: lbruun ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c95f4c... ) Db2 LUW supports lock timeouts as of v11.5.6. Ref: * [ Hibernate ORM source code link| https://github.com/hibernate/hibernate-orm/blob/b18c967cf60b492a4f8f651f5... ] * [IBM Db2 documentation link |https:// github www. ibm. com/ hibernate docs / hibernate-orm en / blob db2 / b18c967cf60b492a4f8f651f58dc42daf6c34db0/hibernate-core/src/main/java/org/hibernate/dialect/DB2Dialect 11. java#L508|smart 5?topic=statement - link concurrent-access-resolution-clause ] (addition of {{WAIT X}} clause) ( https://hibernate.atlassian.net/browse/HHH-15475#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15475#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#100206- sha1:3ac329d )

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-15475) Db2 now support lock timeout (as of v11.5.6)

by lbruun (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HSEARCH-3513) Entity change event sourcing through Debezium

by Yoann Rodière (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HSEARCH-3313) Dynamic index "partitioning"

by Yoann Rodière (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-15474) Calendar might be written with wrong values

by Matthias.Frank (JIRA)

Matthias.Frank ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63119c9... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMDRkZjE0MGNl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15474?atlOrigin=eyJpIjoiMDRkZj... ) HHH-15474 ( https://hibernate.atlassian.net/browse/HHH-15474?atlOrigin=eyJpIjoiMDRkZj... ) Calendar might be written with wrong values ( https://hibernate.atlassian.net/browse/HHH-15474?atlOrigin=eyJpIjoiMDRkZj... ) Issue Type: Bug Affects Versions: 5.3.13 Assignee: Unassigned Components: hibernate-core Created: 01/Sep/2022 23:22 PM Environment: java 1.8; usage of mixed timezones (client%server application). Priority: Major Reporter: Matthias.Frank ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63119c9... ) Hello, when writing Calendar values we experienced, that all values are written in the wrong timezone to the database. All values were shifted by an offset, which is related to the original timezone of the Calendar object. This behavior is critical, since we can’t control by 100% the Calendar values by ourself. We tried to use the jdbcTimeZone settings as well the user.timeZone setting - nothing worked for use. The root cause is related to the TimestampTypeDescriptor (getBinder, doBind). In both methods the Calendar type has a special handling. The configured jdbcTimezon is ignored and the reference timezon for storing the data is taken from the Calendar object itself. Based on the nature of the Calendar object, this is critical. As timestamp with timezone the offset should apply and at least the default timezone should be used. The current handling is an appraoch, which is correct for local time (LocalDateTime), Solution: at least the jdbcTimezone should also apply to the Calendar type. If jdbcTimezone is not specified the configured default timezone should being used as 3rd parameter for PreparedStatement.setTimeStamp and CallableStatement::setTimestamp. Thanks a lot for all Your hibernate support and the excellent ORM solution. Best regards, Matthias ( https://hibernate.atlassian.net/browse/HHH-15474#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15474#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#100206- sha1:3ac329d )

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-15473) Instantiate collections in the default fetch group by default

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZGQ2YWExMjU2... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15473?atlOrigin=eyJpIjoiZGQ2YW... ) HHH-15473 ( https://hibernate.atlassian.net/browse/HHH-15473?atlOrigin=eyJpIjoiZGQ2YW... ) Instantiate collections in the default fetch group by default ( https://hibernate.atlassian.net/browse/HHH-15473?atlOrigin=eyJpIjoiZGQ2YW... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Follows up on [https://hibernate.atlassian.net/browse/HHH-14238|https://hibernate.atlass...]. Setting the default for {{ enable enableCollectionInDefaultFetchGroup }} to {{true}} instead of {{false}} would fix problems such as [quarkusio/quarkus#27657|https://github.com/quarkusio/quarkus/discussions/...], where calling a getter to retrieve a collection on an initialized entity would throw a {{LazyInitializationException}}, whereas one would expect the exception to be thrown later, when accessing the collection itself ({{.size()}}, {{.iterator()}}, ...). Changing the default was suggested when the option was introduced some time ago: [hibernate/hibernate-orm#3558 (comment)|https://github.com/hibernate/hibernate-orm/pull/3558#issuecommen...], [hibernate/hibernate-orm#3558 (comment)|https://github.com/hibernate/hibernate-orm/pull/3558#issuecommen...] ( https://hibernate.atlassian.net/browse/HHH-15473#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15473#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#100206- sha1:41d1dbf )

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-15356) Unable to get primary information on some dialects (ex: Oracle) when the PK column's position doesn't match the alphabetical name's order

by Andrea Boriero (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-15427) [EntityGraph - SubGraph] doesn't fetch data when declare more than 2 levels subgraph

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15427 ( https://hibernate.atlassian.net/browse/HHH-15427?atlOrigin=eyJpIjoiZmVmYT... ) Re: [EntityGraph - SubGraph] doesn't fetch data when declare more than 2 levels subgraph ( https://hibernate.atlassian.net/browse/HHH-15427?atlOrigin=eyJpIjoiZmVmYT... ) Hi Lưu Mạnh Duy ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6135970... ) , I'm going to close this issue, in case you'll managed to reproduce it please open a new Jira and assign it to me. Thanks ( https://hibernate.atlassian.net/browse/HHH-15427#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15427#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#100206- sha1:41d1dbf )

1 year, 8 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