March 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16281) Inconsistent Behaivor of L2 cache between Hibernate 5 and 6

by Christian Beikov (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-16334) Persisting and loading an entity with a null all-delete-orphan collection results in error

by Christian Beikov (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-16319) H6: Problem with order insert to table with batch is ON

by Danilov Roman (JIRA)

Danilov Roman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) *commented* on HHH-16319 ( https://hibernate.atlassian.net/browse/HHH-16319?atlOrigin=eyJpIjoiYzg2Zm... ) Re: H6: Problem with order insert to table with batch is ON ( https://hibernate.atlassian.net/browse/HHH-16319?atlOrigin=eyJpIjoiYzg2Zm... ) In the process of testing the solutions that were described here, another problem appeared: https://hibernate.atlassian.net/browse/HHH-16367 ( https://hibernate.atlassian.net/browse/HHH-16367 ) ( https://hibernate.atlassian.net/browse/HHH-16319#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16319#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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

[JIRA] (HHH-16367) H6: Problem with flush and batch is ON

by Danilov Roman (JIRA)

Danilov Roman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNWQ5NTQ4YjUz... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16367?atlOrigin=eyJpIjoiNWQ5NT... ) HHH-16367 ( https://hibernate.atlassian.net/browse/HHH-16367?atlOrigin=eyJpIjoiNWQ5NT... ) H6: Problem with flush and batch is ON ( https://hibernate.atlassian.net/browse/HHH-16367?atlOrigin=eyJpIjoiNWQ5NT... ) Issue Type: Bug Affects Versions: 6.2.0.CR4 Assignee: Unassigned Attachments: hibernate-orm-6.zip Components: hibernate-core Created: 24/Mar/2023 07:32 AM Priority: Major Reporter: Danilov Roman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) Hello. I have two entites: @Entity @DynamicUpdate @Table(name = "laterals") public class Lateral extends Well implements Serializable { @Column(name = "id", insertable = false, updatable = false, nullable = false, columnDefinition = "serial") @Generated(GenerationTime.INSERT) public Long id; public Long diameter; public Long diameter1; public String paka1; public String paka2; } and @Entity @DynamicUpdate @Table(name = "wells") @Inheritance(strategy = InheritanceType.JOINED) public class Well { @Id public UUID uuid; public String name; public String name1; public String name2; public long gui1; public long gui2; } And when first we select one Lateral , String hql = "from `Lateral` where uuid = ?1"; Query query = entityManager.createQuery(hql); query.setParameter(1, uuid); Lateral lateral = (Lateral) query.getSingleResult(); In the console showed select request. select * from laterals ... Then we are begining to change element’s params: lateral.setName("TEST2"); lateral.setName1("TEST12"); Then we make another any select request: String hql2 = "from Well where uuid = ?1"; Query query2 = entityManager.createQuery(hql2); query2.setParameter(1, uuid); Object object = query2.getSingleResult(); In the console we see update query (with two changed params) and second select query: update wells set name=?, name1=? where uuid=? select * from wells ... Then we are changing more parameters and do persist and flush: lateral.setDiameter(55L); lateral.setDiameter1(55L); lateral.setPaka1("PAKA1"); lateral.setPaka1("PAKA2"); lateral.setName("TEST3"); lateral.setName1("TEST13"); lateral.setName2("TEST23"); lateral.setGui1(111L); lateral.setGui2(222L); entityManager.persist(lateral); entityManager.flush(); And In the console we see update query (with *two* *old params* ) and error: update wells set name=?, name1=? where uuid=? 2023-03-24 18:21:13 TRACE bind:28 - binding parameter [1] as [BIGINT] - [111] 2023-03-24 18:21:13 TRACE bind:28 - binding parameter [2] as [BIGINT] - [222] 2023-03-24 18:21:13 TRACE bind:28 - binding parameter [3] as [VARCHAR] - [TEST3] 2023-03-24 18:21:13 TRACE bind:28 - binding parameter [4] as [VARCHAR] - [TEST13] 2023-03-24 18:21:13 WARN SqlExceptionHelper:145 - SQL Error: 90008, SQLState: 90008 2023-03-24 18:21:13 ERROR SqlExceptionHelper:150 - Invalid value "4" for parameter "parameterIndex" [90008-214] 1) It turns out that before the second select request the makes a flush although I didn't call him? 2) and after my flush it makes the old update request but with new list of parameters. Without “batch” everything works without errors (and on hibernate 5 too). Test cases attached. ( https://hibernate.atlassian.net/browse/HHH-16367#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16367#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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

[JIRA] (HHH-304) Subselect fetching with setMaxResults()

by Ivan Stanic (JIRA)

Ivan Stanic ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5eadd5a... ) *commented* on HHH-304 ( https://hibernate.atlassian.net/browse/HHH-304?atlOrigin=eyJpIjoiOTg3NTU5... ) Re: Subselect fetching with setMaxResults() ( https://hibernate.atlassian.net/browse/HHH-304?atlOrigin=eyJpIjoiOTg3NTU5... ) Hi Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) , Sorry for late reply. I think that adding some config that would control this behavior is way to go, and by default it would not be applicable. I see that there are following options: * Introduce 2 options, one to apply the limit to subquery, another to check for correspondence of data. With this setup one who uses SNAPSHOT or SERIALIZABLE transaction isolation levels can go with true and false, and the one who uses READ_COMMITED can go with true and true options. SUBQUERY_APPLY_LIMIT SUBQUERY_CHECK_CORRESPONDENCE SNAPSHOT or SERIALIZABLE true false READ_COMMITED true true With this parametrization we would avoid additional correspondence check if not necessary. If SUBQUERY_CHECK_CORRESPONDENCE is true, and some data is found that does not belong here than another query can be executed with no limit option. 2. Introduce only SUBQUERY_APPLY_LIMIT and always check for correspondence. This would introduce some not needed check in case of transactions levels SNAPSHOT or SERIALIZABLE 3. Introduce only SUBQUERY_APPLY_LIMIT and never check for correspondence by default. This should be followed with some documentation that this should be used only if transaction isolation levels are SNAPSHOT or SERIALIZABLE 4. Do not use any options, always apply limit and always check for correspondence. I am in favor of the option 1 as the one with the most flexibility but other options are fine as well. Regards, Ivan ( https://hibernate.atlassian.net/browse/HHH-304#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-304#add-comment?atlOrigin=eyJp... ) 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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

[JIRA] (HHH-16337) EntityCollection is not deleted when replaced

by Steve Ebersole (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-16097) Move all tests from documentation into hibernate-core

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *resolved* as *Fixed* Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZjg3MzA3Y2Q5... ) / New Feature ( https://hibernate.atlassian.net/browse/HHH-16097?atlOrigin=eyJpIjoiZjg3Mz... ) HHH-16097 ( https://hibernate.atlassian.net/browse/HHH-16097?atlOrigin=eyJpIjoiZjg3Mz... ) Move all tests from documentation into hibernate-core ( https://hibernate.atlassian.net/browse/HHH-16097?atlOrigin=eyJpIjoiZjg3Mz... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Resolution: Fixed Status: Open Resolved ( https://hibernate.atlassian.net/browse/HHH-16097#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16097#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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

[JIRA] (HHH-16097) Move all tests from documentation into hibernate-core

by Steve Ebersole (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-16339) Consolidate DiscriminatorType, DiscriminatorMetadata, MetadataTpe

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=eyJpIjoiYmVjNmIyMGRh... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16339?atlOrigin=eyJpIjoiYmVjNm... ) HHH-16339 ( https://hibernate.atlassian.net/browse/HHH-16339?atlOrigin=eyJpIjoiYmVjNm... ) Consolidate DiscriminatorType, DiscriminatorMetadata, MetadataTpe ( https://hibernate.atlassian.net/browse/HHH-16339?atlOrigin=eyJpIjoiYmVjNm... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) At the moment, Hibernate is using a mix of new and legacy descriptors for mapping entity discriminators. The legacy contracts include: * {{org.hibernate.persister.entity.DiscriminatorMetadata}} * {{org.hibernate.persister.entity.DiscriminatorType}} * {{org.hibernate.type.MetaType}} The corresponding new runtime mapping contract is: * {{org.hibernate.metamodel.mapping.EntityDiscriminatorMapping}} * {{org.hibernate.metamodel.mapping.internal.AnyDiscriminatorPart}} Much of the consolidation happens through the shared converter - {{org.hibernate.metamodel.mapping.DiscriminatorConverter}} ( https://hibernate.atlassian.net/browse/HHH-16339#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16339#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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

[JIRA] (HHH-16339) Consolidate DiscriminatorType, DiscriminatorMetadata, MetadataTpe

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=eyJpIjoiYTQxMTc3Njgx... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16339?atlOrigin=eyJpIjoiYTQxMT... ) HHH-16339 ( https://hibernate.atlassian.net/browse/HHH-16339?atlOrigin=eyJpIjoiYTQxMT... ) Consolidate DiscriminatorType, DiscriminatorMetadata, MetadataTpe ( https://hibernate.atlassian.net/browse/HHH-16339?atlOrigin=eyJpIjoiYTQxMT... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) At the moment, Hibernate is using a mix of new and legacy descriptors for mapping entity discriminators. The legacy contracts include: * {{org.hibernate.persister.entity.DiscriminatorMetadata}} * {{org.hibernate.persister.entity.DiscriminatorType}} * {{org.hibernate.type.MetaType}} The corresponding new runtime mapping contract is: * {{org.hibernate.metamodel.mapping.EntityDiscriminatorMapping}} * {{org.hibernate.metamodel.mapping.internal.AnyDiscriminatorPart}} ( https://hibernate.atlassian.net/browse/HHH-16339#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16339#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#100219- sha1:ac3e918 )

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