February 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-15876) Fetch type eager issue on entity with @DiscriminatorValue

by Florence Watry (JIRA)

Florence Watry ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=639ae0f... ) *commented* on HHH-15876 ( https://hibernate.atlassian.net/browse/HHH-15876?atlOrigin=eyJpIjoiZjA4ZT... ) Re: Fetch type eager issue on entity with @DiscriminatorValue ( https://hibernate.atlassian.net/browse/HHH-15876?atlOrigin=eyJpIjoiZjA4ZT... ) I updated Hibernate version to 6.1.7 and it still occurs. Here’s the repo to reproduce : https://github.com/FloWat/hibernate6bug ( https://github.com/FloWat/hibernate6bug ) The same code works fine with Hibernate 5.4.10 ( https://hibernate.atlassian.net/browse/HHH-15876#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15876#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#100216- sha1:3fa9804 )

3 years, 1 month

1
0
0 / 0

[JIRA] (HHH-16192) Hibernate Envers triggers wrong column type during validation

by Martin Polanka (JIRA)

Martin Polanka ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYjg5NWU1MDkx... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16192?atlOrigin=eyJpIjoiYjg5NW... ) HHH-16192 ( https://hibernate.atlassian.net/browse/HHH-16192?atlOrigin=eyJpIjoiYjg5NW... ) Hibernate Envers triggers wrong column type during validation ( https://hibernate.atlassian.net/browse/HHH-16192?atlOrigin=eyJpIjoiYjg5NW... ) Change By: Martin Polanka ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I have a Spring Boot project which I updated to SB3, before everything worked, but after update I am getting schema-validation error in audit tables. Minimal sample project can be found here [ https://github.com/Neloop/sb3-hibernate-envers-demo |https://github.com/Neloop/sb3-hibernate-envers-demo] The project uses * liquibase * as migration tool and with it the database structure is created, in this case there is only one table 'demo' and two audit tables. If I try to run the project I get: {code:java} org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: wrong column type encountered in column [description] in table [demo_aud]; found [character (Types#CLOB)], but expecting [varchar(255) (Types#VARCHAR)] {code} Which is unexpected because on the *DemoEntity* there is column *description* which has *@Lob* annotation and therefore its type should definitely not be VARCHAR(255), but it seems that envers metadata thinks that it is. It seems like a regression, because as I said this was working before I updated to SB3 with Hibernate 6.1 ( https://hibernate.atlassian.net/browse/HHH-16192#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16192#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#100216- sha1:3fa9804 )

3 years, 1 month

1
0
0 / 0

[JIRA] (HHH-16192) Hibernate Envers triggers wrong column type during validation

by Martin Polanka (JIRA)

Martin Polanka ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMDE5OWEwZWM3... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16192?atlOrigin=eyJpIjoiMDE5OW... ) HHH-16192 ( https://hibernate.atlassian.net/browse/HHH-16192?atlOrigin=eyJpIjoiMDE5OW... ) Hibernate Envers triggers wrong column type during validation ( https://hibernate.atlassian.net/browse/HHH-16192?atlOrigin=eyJpIjoiMDE5OW... ) Issue Type: Bug Affects Versions: 6.1.6 Assignee: Chris Cranford ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: hibernate-envers Created: 17/Feb/2023 01:30 AM Environment: JVM: temurin-17 OS: Win10 DB: h2 Priority: Major Reporter: Martin Polanka ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I have a Spring Boot project which I updated to SB3, before everything worked, but after update I am getting schema-validation error in audit tables. Minimal sample project can be found here https://github.com/Neloop/sb3-hibernate-envers-demo ( https://github.com/Neloop/sb3-hibernate-envers-demo ) The project uses liquibase as migration tool and with it the database structure is created, in this case there is only one table 'demo' and two audit tables. If I try to run the project I get: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: wrong column type encountered in column [description] in table [demo_aud]; found [character (Types#CLOB)], but expecting [varchar(255) (Types#VARCHAR)] Which is unexpected because on the *DemoEntity* there is column *description* which has *@Lob* annotation and therefore its type should definitely not be VARCHAR(255), but it seems that envers metadata thinks that it is. It seems like a regression, because as I said this was working before I updated to SB3 with Hibernate 6.1 ( https://hibernate.atlassian.net/browse/HHH-16192#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16192#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#100216- sha1:3fa9804 )

3 years, 1 month

1
0
0 / 0

[JIRA] (HHH-16191) Since Hibernate ORM 6.x the FetchType.EAGER called from native queries raises error

by davide ficano (JIRA)

davide ficano ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a673f0... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOGU2ZWZmZjhk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16191?atlOrigin=eyJpIjoiOGU2ZW... ) HHH-16191 ( https://hibernate.atlassian.net/browse/HHH-16191?atlOrigin=eyJpIjoiOGU2ZW... ) Since Hibernate ORM 6.x the FetchType.EAGER called from native queries raises error ( https://hibernate.atlassian.net/browse/HHH-16191?atlOrigin=eyJpIjoiOGU2ZW... ) Change By: davide ficano ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a673f0... ) Since Hibernate ORM 6.x the {{FetchType.EAGER}} raises the following error when called from native queries {noformat}could not initialize proxy [org.hibernate.domain.Building#0] - no Session {noformat} Using the same {{@Entity}} with hibernate {{createQuery()}}, everything works as expected I’ve create created a test case [available on github|https://github.com/unipa/Hibernate-Native-Query-EAGER-regression] After cloning the repo, just run {{mvn package}} ( https://hibernate.atlassian.net/browse/HHH-16191#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16191#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#100216- sha1:3fa9804 )

3 years, 1 month

1
0
0 / 0

[JIRA] (HHH-16191) Since Hibernate ORM 6.x the FetchType.EAGER called from native queries raises error

by davide ficano (JIRA)

davide ficano ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a673f0... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGYzZDY5YTNl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16191?atlOrigin=eyJpIjoiNGYzZD... ) HHH-16191 ( https://hibernate.atlassian.net/browse/HHH-16191?atlOrigin=eyJpIjoiNGYzZD... ) Since Hibernate ORM 6.x the FetchType.EAGER called from native queries raises error ( https://hibernate.atlassian.net/browse/HHH-16191?atlOrigin=eyJpIjoiNGYzZD... ) Issue Type: Bug Affects Versions: 6.1.7 Assignee: Unassigned Components: hibernate-orm-modules Created: 17/Feb/2023 00:43 AM Environment: Hibernate 6.1.7 openjdk version "17.0.6" 2023-01-17 MacOS Ventura 13.2.1 Any Database Priority: Major Reporter: davide ficano ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a673f0... ) Since Hibernate ORM 6.x the FetchType.EAGER raises the following error when called from native queries could not initialize proxy [org.hibernate.domain.Building#0] - no Session Using the same @Entity with hibernate createQuery() , everything works as expected I’ve create a test case available on github ( https://github.com/unipa/Hibernate-Native-Query-EAGER-regression ) After cloning the repo, just run mvn package ( https://hibernate.atlassian.net/browse/HHH-16191#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16191#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#100216- sha1:3fa9804 )

3 years, 1 month

1
0
0 / 0

[JIRA] (HHH-16190) Update the GraalVM module to match the reflective needs of StandardStack

by Sanne Grinovero (JIRA)

3 years, 1 month

1
0
0 / 0

[JIRA] (HHH-16190) Update the GraalVM module to match the reflective needs of StandardStack

by Sanne Grinovero (JIRA)

3 years, 1 month

1
0
0 / 0

[JIRA] (HHH-16119) Named native queries do not work with jakarta.persistence.Tuple result class

by Sauli Anto (JIRA)

Sauli Anto ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16119 ( https://hibernate.atlassian.net/browse/HHH-16119?atlOrigin=eyJpIjoiNTY1MD... ) Re: Named native queries do not work with jakarta.persistence.Tuple result class ( https://hibernate.atlassian.net/browse/HHH-16119?atlOrigin=eyJpIjoiNTY1MD... ) Thank you Andrea for the fix. I think I noticed a small typo in the test class. @TestForIssue(jiraKey = "HHH-16199") probably should be @TestForIssue(jiraKey = "HHH-16119") ( https://github.com/hibernate/hibernate-orm/commit/41961d457a068940c10ed40... ( https://github.com/hibernate/hibernate-orm/commit/41961d457a068940c10ed40... ) ) ( https://hibernate.atlassian.net/browse/HHH-16119#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16119#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#100216- sha1:a0b8fe5 )

3 years, 1 month

1
0
0 / 0

[JIRA] (HHH-16190) Update the GraalVM module to match the reflective needs of StandardStack

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYjM5YTdiNjRk... ) / Task ( https://hibernate.atlassian.net/browse/HHH-16190?atlOrigin=eyJpIjoiYjM5YT... ) HHH-16190 ( https://hibernate.atlassian.net/browse/HHH-16190?atlOrigin=eyJpIjoiYjM5YT... ) Update the GraalVM module to match the reflective needs of StandardStack ( https://hibernate.atlassian.net/browse/HHH-16190?atlOrigin=eyJpIjoiYjM5YT... ) Issue Type: Task Assignee: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: hibernate-graalvm Created: 16/Feb/2023 11:50 AM Fix Versions: 6.2.0 Priority: Critical Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The newly introduced internal collection StandardStack triggers a need for reflective allocations of arrays; GraalVM is unable to handle this automatically, so we should update the hibernate-graalvm to reflect this. ( https://hibernate.atlassian.net/browse/HHH-16190#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16190#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#100216- sha1:a0b8fe5 )

3 years, 1 month

1
0
0 / 0

[JIRA] (HHH-16165) Incorrect SQL generated when using SELECT DISTINCT and @OrderBy

by Mirek Jezbera (JIRA)

Mirek Jezbera ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63d2a4d... ) *commented* on HHH-16165 ( https://hibernate.atlassian.net/browse/HHH-16165?atlOrigin=eyJpIjoiNGJiND... ) Re: Incorrect SQL generated when using SELECT DISTINCT and @OrderBy ( https://hibernate.atlassian.net/browse/HHH-16165?atlOrigin=eyJpIjoiNGJiND... ) I think this affects hibernate 6.1, too. ( https://hibernate.atlassian.net/browse/HHH-16165#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16165#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#100216- sha1:a0b8fe5 )

3 years, 1 month

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