April 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16436) Hibernate 6 - Numeric Overflow Exception when retrieving the Meta-data for sequences from Oracle Database

by Flash Vayne (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-16436) Hibernate 6 - Numeric Overflow Exception when retrieving the Meta-data for sequences from Oracle Database

by Flash Vayne (JIRA)

Flash Vayne ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNWJlODkxY2Jl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16436?atlOrigin=eyJpIjoiNWJlOD... ) HHH-16436 ( https://hibernate.atlassian.net/browse/HHH-16436?atlOrigin=eyJpIjoiNWJlOD... ) Hibernate 6 - Numeric Overflow Exception when retrieving the Meta-data for sequences from Oracle Database ( https://hibernate.atlassian.net/browse/HHH-16436?atlOrigin=eyJpIjoiNWJlOD... ) Change By: Flash Vayne ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) When I upgrade Hibernate from 5 to 6, Numeric Overflow Exception occurs. *Database Column:* NUMBER(10,0) *Column data:* '3876543210' *SQL:* !p1.png|width=449,height=68! *Exception:* !p2.png|width=1367,height=145! I found that the org.hibernate.OracleDialect always select Integer as JdbcType when precision = 10. !image-20230406-040731.png|width=832,height=437! Actually '3876543210' is not a Integer data but can be saved in column NUMER(10,0). So I think it’s a bug, can you please help check it? ( https://hibernate.atlassian.net/browse/HHH-16436#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16436#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#100221- sha1:78e8bd6 )

3 years

1
0
0 / 0

[JIRA] (HHH-16436) Hibernate 6 - Numeric Overflow Exception when retrieving the Meta-data for sequences from Oracle Database

by Flash Vayne (JIRA)

Flash Vayne ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZDdhNjdlZjJj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16436?atlOrigin=eyJpIjoiZDdhNj... ) HHH-16436 ( https://hibernate.atlassian.net/browse/HHH-16436?atlOrigin=eyJpIjoiZDdhNj... ) Hibernate 6 - Numeric Overflow Exception when retrieving the Meta-data for sequences from Oracle Database ( https://hibernate.atlassian.net/browse/HHH-16436?atlOrigin=eyJpIjoiZDdhNj... ) Change By: Flash Vayne ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) When I upgrade Hibernate from 5 to 6, Numeric Overflow Exception occurs. *Database Column:* NUMBER(10,0) *Column data:* '3876543210' * SQL: * !p1.png|width=449,height=68! * Exception: * !p2.png|width=1367,height=145! I found that the org.hibernate.OracleDialect always was set to default Dialect select Integer as JdbcType when precision = 10. If I change org.hibernate.OracleDialect to org.hibernate.MariaDBDialect, it works. I think there is a bug in org.hibernate.OracleDialect, but I can’t change it to older OracleDialect like Oracle10gDialect due to the reason in below alert ! p3 image-20230406-040731.png|width= 790 832 ,height= 50 437 ! Also I try all the hibernate 6.x version Actually '3876543210' is not a Integer data but can be saved in column NUMER(10 , neither works 0). So I think it’s bug, can you please help check it? ( https://hibernate.atlassian.net/browse/HHH-16436#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16436#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#100221- sha1:78e8bd6 )

3 years

1
0
0 / 0

[JIRA] (HHH-16441) Implement BatchFetchStrategy-like support for @BatchSize

by Steve Ebersole (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-16411) CollectionLoaderBatchKey seems to always translate SQL instead of caching

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16411 ( https://hibernate.atlassian.net/browse/HHH-16411?atlOrigin=eyJpIjoiMGZiYz... ) Re: CollectionLoaderBatchKey seems to always translate SQL instead of caching ( https://hibernate.atlassian.net/browse/HHH-16411?atlOrigin=eyJpIjoiMGZiYz... ) It does cache the SQL provided there is actually more than one key to load. If there is a single id to load, yes it currently does not cache that SQL ( https://hibernate.atlassian.net/browse/HHH-16411#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16411#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#100221- sha1:78e8bd6 )

3 years

1
0
0 / 0

[JIRA] (HHH-16441) Implement BatchFetchStrategy-like support for @BatchSize

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16441 ( https://hibernate.atlassian.net/browse/HHH-16441?atlOrigin=eyJpIjoiMDEzZT... ) Re: Implement BatchFetchStrategy-like support for @BatchSize ( https://hibernate.atlassian.net/browse/HHH-16441?atlOrigin=eyJpIjoiMDEzZT... ) I just implemented the following strategies: * if hibernate.query.in_clause_parameter_padding is enabled, a modified version of the legacy “coin change algorithm” approach is used - the modification is to use padding within each partition - SingleIdEntityPartitionedBatchLoader * Otherwise, generally, a “static SQL” approach is used where we use a single SQL with batch-size number of parameters, with null padding for “empty slots” - SingleIdEntityPaddedBatchLoader * Also implemented a dynamic approach where we create SQL on the fly each time for the specific number of ids. Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) also suggested possibly using an array parameter which I also like. I think we should limit the options here a bit though. Does anyone see the benefit of the dynamic approach? To me, “static SQL” and array-parameter would be enough; maybe with a fallback to partitioned if the “static SQL” batch-size exceeds a certain limit? ( https://hibernate.atlassian.net/browse/HHH-16441#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16441#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#100221- sha1:78e8bd6 )

3 years

1
0
0 / 0

[JIRA] (HHH-16442) trunc() function with offset datetimes 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=eyJpIjoiNzM4ZWMwNTZk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16442?atlOrigin=eyJpIjoiNzM4ZW... ) HHH-16442 ( https://hibernate.atlassian.net/browse/HHH-16442?atlOrigin=eyJpIjoiNzM4ZW... ) trunc() function with offset datetimes on Oracle ( https://hibernate.atlassian.net/browse/HHH-16442?atlOrigin=eyJpIjoiNzM4ZW... ) Issue Type: Bug Affects Versions: 6.2.0 Assignee: Unassigned Components: query-hql Created: 05/Apr/2023 16:09 PM Priority: Minor Reporter: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The Oracle trunc() function throws away any offset in its argument, so queries like: select truncate(offset datetime 1974-10-03 12:30-12:00, day) return the wrong result. The query above works correctly on all the other databases we test. ( https://hibernate.atlassian.net/browse/HHH-16442#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16442#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#100221- sha1:78e8bd6 )

3 years

1
0
0 / 0

[JIRA] (HHH-16389) Introduce annotations for nullness marking/checking

by Christian Beikov (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-16441) Implement BatchFetchStrategy-like support for @BatchSize

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYWQ5MWNjNTNk... ) / Deprecation ( https://hibernate.atlassian.net/browse/HHH-16441?atlOrigin=eyJpIjoiYWQ5MW... ) HHH-16441 ( https://hibernate.atlassian.net/browse/HHH-16441?atlOrigin=eyJpIjoiYWQ5MW... ) Implement BatchFetchStrategy-like support for @BatchSize ( https://hibernate.atlassian.net/browse/HHH-16441?atlOrigin=eyJpIjoiYWQ5MW... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) During the development of 6.x, support for {{BatchFetchStrategy}} as applied to {{@BatchSize}} for entity and collection fetches was not ported due to time constraints. In the interim, {{BatchFetchStrategy}} was deprecated. Which is fine. I think the strategy for entity and collection batch fetching should be a mix {{DYNAMIC}} and {{PADDED}}, based on the outcome of the underlying {{Dialect#getDefaultBatchLoadSizingStrategy}} The current implementation implements the {{DYNAMIC}} strategy. Implement support for When {{PADDED}} is used, we should cache the generated SQL AST. When {{ LEGACY DYNAMIC }} ? , we should maybe offer some limited caching of SQL AST(s). ( https://hibernate.atlassian.net/browse/HHH-16441#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16441#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#100221- sha1:78e8bd6 )

3 years

1
0
0 / 0

[JIRA] (HHH-16441) Implement BatchFetchStrategy-like support for @BatchSize

by Steve Ebersole (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 April 2023