May 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16589) In-Clause Parameter Padding mistreats Dilect.getInExpressionCountLimit which can cause ORA-01795: maximum number of expressions in a list is 1000

by Adrodoc (JIRA)

Adrodoc ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b2a4a0... ) *commented* on HHH-16589 ( https://hibernate.atlassian.net/browse/HHH-16589?atlOrigin=eyJpIjoiYWY3NG... ) Re: In-Clause Parameter Padding mistreats Dilect.getInExpressionCountLimit which can cause ORA-01795: maximum number of expressions in a list is 1000 ( https://hibernate.atlassian.net/browse/HHH-16589?atlOrigin=eyJpIjoiYWY3NG... ) While coding a fix I noticed two additional Bugs in this code: * For a NOT-IN-Clause you would have to use AND instead of OR. Currently Hibernate generates a query like ID not in(?,?,?,?,...) or ID not in }}which is incorrect. It should be {{ID not in(?,?,?,?,...) and ID not in. * No braces are added around multiple in clauses. For example if you have an additional where clause like ID < ? Hibernate generates ID < ? and id in(?,?,...) or id in. This query ignores the first predicate for all IDs in the second in clause. ( https://hibernate.atlassian.net/browse/HHH-16589#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16589#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#100225- sha1:84d3b45 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16578) Incorrect validation error for tinyint, but and datetime

by Jan Schatteman (JIRA)

Jan Schatteman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16578 ( https://hibernate.atlassian.net/browse/HHH-16578?atlOrigin=eyJpIjoiZWI3YW... ) Re: Incorrect validation error for tinyint, but and datetime ( https://hibernate.atlassian.net/browse/HHH-16578?atlOrigin=eyJpIjoiZWI3YW... ) Coercing an integral type into a certain db type is not per sé an error (unless potentially when you put values in it that don’t fit), but the validation shouldn’t fail because unsigned is added to the definition, so this is prob. a legitimate issue, although I still have to look into it to be sure what is going on. ( https://hibernate.atlassian.net/browse/HHH-16578#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16578#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#100225- sha1:84d3b45 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16591) @org.hibernate.annotations.JdbcType does not override the `hibernate.type.preferred_duration_jdbc_type` type

by Marko Bekhta (JIRA)

Marko Bekhta ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYjUwOTZmZDVk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16591?atlOrigin=eyJpIjoiYjUwOT... ) HHH-16591 ( https://hibernate.atlassian.net/browse/HHH-16591?atlOrigin=eyJpIjoiYjUwOT... ) @org.hibernate.annotations.JdbcType does not override the `hibernate.type.preferred_duration_jdbc_type` type ( https://hibernate.atlassian.net/browse/HHH-16591?atlOrigin=eyJpIjoiYjUwOT... ) Issue Type: Bug Affects Versions: 6.2.2 Assignee: Unassigned Components: hibernate-core Created: 11/May/2023 09:49 AM Priority: Major Reporter: Marko Bekhta ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) According to the docs, the config property: PREFERRED_DURATION_JDBC_TYPE = "hibernate.type.preferred_duration_jdbc_type" Can be overridden on a property level by using annotations: > > > > Can be overridden locally using org.hibernate.annotations.JdbcType, > org.hibernate.annotations.JdbcTypeCode, and friends. > > While specifying a particular JdbcType class works as expected: // will result in using the `PostgreSQLIntervalSecondJdbcType` @Column(precision = 10, scale = 6) @org.hibernate.annotations.JdbcType(PostgreSQLIntervalSecondJdbcType.class) private Duration durationJdbcType; Specifying a JdbcType code - has no effect: // still uses the JdbcType configured by the `PREFERRED_DURATION_JDBC_TYPE` property @Column(precision = 10, scale = 6) @JdbcTypeCode(SqlTypes.INTERVAL_SECOND) private Duration durationJdbcTypeCode; I will submit a test case for this one soon. ( https://hibernate.atlassian.net/browse/HHH-16591#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16591#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#100225- sha1:84d3b45 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16572) Incorrect enhancement for PROPERTY attributes with mismatched field and method names

by Steve Ebersole (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16572) Incorrect enhancement for PROPERTY attributes with mismatched field and method names

by Steve Ebersole (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16572) Incorrect enhancement for PROPERTY attributes with mismatched field and method names

by Steve Ebersole (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16590) Schema update: PostgreSQL byte array does not accept length as parameter

by Čedomir Igaly (JIRA)

Čedomir Igaly ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16590 ( https://hibernate.atlassian.net/browse/HHH-16590?atlOrigin=eyJpIjoiMTkzMj... ) Re: Schema update: PostgreSQL byte array does not accept length as parameter ( https://hibernate.atlassian.net/browse/HHH-16590?atlOrigin=eyJpIjoiMTkzMj... ) Test case and suggested solution in PR 6553 ( https://github.com/hibernate/hibernate-orm/pull/6553 ) ( https://hibernate.atlassian.net/browse/HHH-16590#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16590#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#100225- sha1:84d3b45 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16572) Incorrect enhancement for PROPERTY attributes with mismatched field and method names

by Steve Ebersole (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16590) Schema update: PostgreSQL byte array does not accept length as parameter

by Čedomir Igaly (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16590) Schema update: PostgreSQL byte array does not accept length as parameter

by Čedomir Igaly (JIRA)

Čedomir Igaly ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNjM0NDhlOTZj... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16590?atlOrigin=eyJpIjoiNjM0ND... ) HHH-16590 ( https://hibernate.atlassian.net/browse/HHH-16590?atlOrigin=eyJpIjoiNjM0ND... ) Schema update: PostgreSQL byte array does not accept length as parameter ( https://hibernate.atlassian.net/browse/HHH-16590?atlOrigin=eyJpIjoiNjM0ND... ) Issue Type: Improvement Assignee: Unassigned Components: hibernate-core Created: 11/May/2023 08:43 AM Priority: Minor Reporter: Čedomir Igaly ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) In PostgreSQL byte array column (bytea) does not have length parameter. When schema is automatically generaed, it will be correctly generated as bytea. However, during schema update length value from column metadata will be compared with either default value or value from @Column annotation (if present). This will, most likely rhan not, cause alter SQL command to be executed. Data type in this generated command will be exactly the same as one use for table creation. In most cases this will have no effect (except waste of time if PostgreSQL is not “smart” enough to ignore column data type change) but in some situations can cause problems. For example when column is used in view definition. ( https://hibernate.atlassian.net/browse/HHH-16590#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16590#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#100225- sha1:84d3b45 )

2 years, 11 months

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