September 2022 - hibernate-issues

[JIRA] (HHH-15531) Use dense_rank instead of row_number when query uses dinstinct

by Christian Beikov (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15527) Use SimpleInsertQueryPlan when query assigns id even if optimizer increment is bigger than 1

by Christian Beikov (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15517) "insert from select" With hibernate.default_schema Configured Doesn't Work With Hibernate 6

by Christian Beikov (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15490) Remove support for HSQLDB versions older than 2.6.1

by Christian Beikov (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HBX-2398) Update Hibernate ORM Dependency to Version 5.6.12.Final

by Koen Aers (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15511) CockroachDB dialect version incorrectly determined

by Christian Beikov (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15530) Lazy loading is not working when @NotFound IGNORE is used

by Christian Beikov (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15530) Lazy loading is not working when @NotFound IGNORE is used

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15530 ( https://hibernate.atlassian.net/browse/HHH-15530?atlOrigin=eyJpIjoiYTQwZD... ) Re: Lazy loading is not working when @NotFound IGNORE is used ( https://hibernate.atlassian.net/browse/HHH-15530?atlOrigin=eyJpIjoiYTQwZD... ) Read the updated documentation section about the @NotFound mapping: https://docs.jboss.org/hibernate/orm/5.6/userguide/html_single/Hibernate_... ( https://docs.jboss.org/hibernate/orm/5.6/userguide/html_single/Hibernate_... ) This is a bug fix, as the way this worked before was broken. NotFoundAction.IGNORE simply can't work with FetchType.LAZY , because in order to ignore a missing target row, the target row must be joined so that we can see if it exists. NotFoundAction.EXCEPTION is a way to eagerly throw an exception, but usually, when you use FetchType.LAZY with a broken FK value and without the @NotFound mapping, you will get an exception when loading that proxy on first access. If you want broken proxies that produce an exception on first access, then simply remove the @NotFound annotation. ( https://hibernate.atlassian.net/browse/HHH-15530#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15530#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#100207- sha1:866f7d8 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15530) Lazy loading is not working when @NotFound IGNORE is used

by Jiayin Mao (JIRA)

Jiayin Mao ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b4e4c5... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNWQ1NGQ5MjM5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15530?atlOrigin=eyJpIjoiNWQ1NG... ) HHH-15530 ( https://hibernate.atlassian.net/browse/HHH-15530?atlOrigin=eyJpIjoiNWQ1NG... ) Lazy loading is not working when @NotFound IGNORE is used ( https://hibernate.atlassian.net/browse/HHH-15530?atlOrigin=eyJpIjoiNWQ1NG... ) Issue Type: Bug Affects Versions: 5.6.6 Assignee: Unassigned Components: hibernate-core Created: 19/Sep/2022 18:34 PM Priority: Blocker Reporter: Jiayin Mao ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b4e4c5... ) In our application we are using @ManyToMany(fetch = FetchType.LAZY) on an association and we are also using @NotFound(action = NotFoundAction.IGNORE) since there are some non-existing referenced objects in the database. After upgrading to 5.6.6, the associated objects are eagerly loaded, causing the corresponding feature to be slowed down by 500 to 1000 times. This behavior change seems to be caused by the fix of https://hibernate.atlassian.net/browse/HHH-15060 ( https://hibernate.atlassian.net/browse/HHH-15060 ) , in which lazy load is disabled when @NotFound is specified (source here ( https://github.com/hibernate/hibernate-orm/blob/64272ba56173c5a723353741e... ) ). Due to the limit of existing data we have to NotFoundAction.IGNORE so this is a blocking issue for us. ( https://hibernate.atlassian.net/browse/HHH-15530#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15530#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#100207- sha1:866f7d8 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15517) "insert from select" With hibernate.default_schema Configured Doesn't Work With Hibernate 6

by Kai Zander (JIRA)

Kai Zander ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15517 ( https://hibernate.atlassian.net/browse/HHH-15517?atlOrigin=eyJpIjoiYWJlMj... ) Re: "insert from select" With hibernate.default_schema Configured Doesn't Work With Hibernate 6 ( https://hibernate.atlassian.net/browse/HHH-15517?atlOrigin=eyJpIjoiYWJlMj... ) I experimented a bit more and found the following: If I rewrite the HQL to this (don’t select id , use distinct instead of group by ): insert into TabData (col1, col2, col3) select distinct col1, col2, col3 from TabDataStaging Hibernate 6 does the following: insert into HTE_tab_data(col1, col2, col3, rn_) ( select distinct p2_0.col1, p2_0.col2, p2_0.col3, row_number () over () -- adding this column effectively disables the ` distinct ` from tab_data_staging p2_0); Followed by the updates on the HTE table you were suspecting earlier: update HTE_tab_data set id=? where rn_=? update HTE_tab_data set id=? where rn_=? ... Followed by insert into tab_data(col1,col2,col3,id) select p1_0.col1,p1_0.col2,p1_0.col3,p1_0.id from HTE_tab_data p1_0 The final insert into tab_data can then fail due to unique constraint violation (I have a composite unique constraint on col1, col2, col3 ), because even though I’m using distinct , the row_number() clause added by Hibernate effectively disabled it… ( https://hibernate.atlassian.net/browse/HHH-15517#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15517#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#100207- sha1:7afd384 )

2 years, 3 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