July 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16950) Bump local-build-plugins Jandex version

by Jan Schatteman (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16947) Upgrade to Narayana 7.0.0.Final

by Sanne Grinovero (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-1661) merge of a deleted object results in a insert?

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-1661 ( https://hibernate.atlassian.net/browse/HHH-1661?atlOrigin=eyJpIjoiYzhkNjI... ) Re: merge of a deleted object results in a insert? ( https://hibernate.atlassian.net/browse/HHH-1661?atlOrigin=eyJpIjoiYzhkNjI... ) Is “current Session” the same throughout? ( https://hibernate.atlassian.net/browse/HHH-1661#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-1661#add-comment?atlOrigin=eyJ... ) 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#100232- sha1:33a7c72 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-1661) merge of a deleted object results in a insert?

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-1661 ( https://hibernate.atlassian.net/browse/HHH-1661?atlOrigin=eyJpIjoiYTcxMzA... ) Re: merge of a deleted object results in a insert? ( https://hibernate.atlassian.net/browse/HHH-1661?atlOrigin=eyJpIjoiYTcxMzA... ) Perhaps I am misunderstanding here, but after the first call above to session.getTransaction().commit(); the entity is not detached. Detached indicates there is a corresponding row in the database, which is not the case here. What am I missing? > > > > If X is a removed entity instance, an IllegalArgumentException will be > thrown by the > merge operation (or the transaction commit will fail). > > That is talking about the removed status, which is true before the flush+commit. After the commit, the entity is gone. ( https://hibernate.atlassian.net/browse/HHH-1661#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-1661#add-comment?atlOrigin=eyJ... ) 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#100232- sha1:33a7c72 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16949) QueryException: Parameter 1 of function max() has type COMPARABLE

by Damian S (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16949) QueryException: Parameter 1 of function max() has type COMPARABLE

by Damian S (JIRA)

Damian S ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ba8d59... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzMzZWIxMDFh... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16949?atlOrigin=eyJpIjoiMzMzZW... ) HHH-16949 ( https://hibernate.atlassian.net/browse/HHH-16949?atlOrigin=eyJpIjoiMzMzZW... ) QueryException: Parameter 1 of function max() has type COMPARABLE ( https://hibernate.atlassian.net/browse/HHH-16949?atlOrigin=eyJpIjoiMzMzZW... ) Change By: Damian S ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ba8d59... ) The code is generating a query: {noformat}select datasourceView.id, max(datasourceView.datasourceStatus) as DATASOURCE_STATUS_helper_column, datasourceView.id as ID_helper_column{noformat} datasourceStatus is an enum mapped to a text column. {noformat}@Column(name = "status") @Enumerated(EnumType.STRING) private DatasourceStatus datasourceStatus;{noformat} As a result I get. {{org.springframework.dao.InvalidDataAccessApiUsageException: org.hibernate.QueryException: Parameter 1 of function max() has type COMPARABLE, but argument is of type com.xxx.datasource.domain.DatasourceStatus}} This query was working in Hibernate 6.1.7 (and 5+ versions). It seems it was introduced in 6.2.0 and it is also present it the latest available version. Chainging Changing the enum definitaion class definition to expliclty explicitly implement comparable interface doesn’t help. ( https://hibernate.atlassian.net/browse/HHH-16949#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16949#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#100232- sha1:33a7c72 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16949) QueryException: Parameter 1 of function max() has type COMPARABLE

by Damian S (JIRA)

Damian S ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ba8d59... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNDcxNWZjNTRj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16949?atlOrigin=eyJpIjoiNDcxNW... ) HHH-16949 ( https://hibernate.atlassian.net/browse/HHH-16949?atlOrigin=eyJpIjoiNDcxNW... ) QueryException: Parameter 1 of function max() has type COMPARABLE ( https://hibernate.atlassian.net/browse/HHH-16949?atlOrigin=eyJpIjoiNDcxNW... ) Change By: Damian S ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ba8d59... ) The code is generating a query: {noformat}select datasourceView.id, max(datasourceView.datasourceStatus) as DATASOURCE_STATUS_helper_column, datasourceView.id as ID_helper_column{noformat} datasourceStatus is an enum mapped to a text column. {noformat}@Column(name = "status") @Enumerated(EnumType.STRING) private DatasourceStatus datasourceStatus;{noformat} As a result I get. {{org.springframework.dao.InvalidDataAccessApiUsageException: org.hibernate.QueryException: Parameter 1 of function max() has type COMPARABLE, but argument is of type com.xxx.datasource.domain.DatasourceStatus}} This query was working in Hibernate 6.1.7 (and 5+ versions). It seems it was introduced in 6.2.0 and it is also present it the latest available version. Chainging the enum definitaion to expliclty implement comparable doesn’t help. ( https://hibernate.atlassian.net/browse/HHH-16949#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16949#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#100232- sha1:33a7c72 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16949) QueryException: Parameter 1 of function max() has type COMPARABLE

by Damian S (JIRA)

Damian S ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ba8d59... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZjM0MzZlMjQ1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16949?atlOrigin=eyJpIjoiZjM0Mz... ) HHH-16949 ( https://hibernate.atlassian.net/browse/HHH-16949?atlOrigin=eyJpIjoiZjM0Mz... ) QueryException: Parameter 1 of function max() has type COMPARABLE ( https://hibernate.atlassian.net/browse/HHH-16949?atlOrigin=eyJpIjoiZjM0Mz... ) Issue Type: Bug Affects Versions: 6.2.0 Assignee: Unassigned Created: 17/Jul/2023 09:03 AM Environment: Hibernate 6.2.0+ Priority: Major Reporter: Damian S ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ba8d59... ) The code is generating a query: select datasourceView.id, max(datasourceView.datasourceStatus) as DATASOURCE_STATUS_helper_column, datasourceView.id as ID_helper_column datasourceStatus is an enum mapped to a text column. @Column(name = "status") @Enumerated(EnumType.STRING) private DatasourceStatus datasourceStatus; As a result I get. org.springframework.dao.InvalidDataAccessApiUsageException: org.hibernate.QueryException: Parameter 1 of function max() has type COMPARABLE, but argument is of type com.xxx.datasource.domain.DatasourceStatus This query was working in Hibernate 6.1.7 (and 5+ versions). It seems it was introduced in 6.2.0 and it is also present it the latest available version. ( https://hibernate.atlassian.net/browse/HHH-16949#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16949#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#100232- sha1:33a7c72 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16790) Performance issue when retrieving a large bulk of entity in bidirectionnal association

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16790 ( https://hibernate.atlassian.net/browse/HHH-16790?atlOrigin=eyJpIjoiNTc2MT... ) Re: Performance issue when retrieving a large bulk of entity in bidirectionnal association ( https://hibernate.atlassian.net/browse/HHH-16790?atlOrigin=eyJpIjoiNTc2MT... ) Thank you everyone that contributed to reporting this issue. We were able to implement a possible fix that will improve performance drastically when many associations with slower data types are involved. This improvement will be available in version 6.3.0. Some performance difference might still be present comparing directly with Hibernate 5, though, as the way we construct queries, join associations and in general fetch entity data has changed quite a bit with version 6. One general recommendation to get around this would be avoiding mapping associations, especially when *to-many* , as FetchType.EAGER and instead explicitly specify what to fetch for each query or load. ( https://hibernate.atlassian.net/browse/HHH-16790#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16790#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#100232- sha1:33a7c72 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16611) Sybase: ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - db.tablename not found

by Steve Ebersole (JIRA)

2 years, 8 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 July 2023