September 2022 - hibernate-issues

[JIRA] (HHH-15159) Orphan removal of an entity with an @ElementCollection causes a ConstraintViolationException

by Christian Beikov (JIRA)

2 years, 6 months

1
0
0 / 0

[JIRA] (HHH-15480) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags

by Artёm Basov (JIRA)

Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMDUzYzdmYjk0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiMDUzYz... ) HHH-15480 ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiMDUzYz... ) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiMDUzYz... ) Change By: Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) This is, in a sense, a combination of [HHH-7918|https://hibernate.atlassian.net/browse/HHH-7918] and [HHH-7948|https://hibernate.atlassian.net/browse/HHH-7948]. Steps: # Tx1: Create {{ ListRefEdEntity SetRefEdEntity }} # Tx2: ## Fetch {{ ListRefEdEntity SetRefEdEntity }} created at (1) ## Create and persist {{ ListRefIngEntity SetRefIngEntity }} associated with {{ ListRefEdEntity SetRefEdEntity }} fetched at (a) ## Change its data , associate with {{ ListRefIngEntity SetRefIngEntity }} ## Flush ## Change its data again This will lead to 2nd revision of {{ ListRefEdEntity SetRefEdEntity }} with {{reffering_mod=false}} See a [PR|https://github.com/hibernate/hibernate-orm/pull/5253] with a test case. We’ve caught this in {{5.4.32}}, but since test case fails on {{main}}, I’m assuming it affects every version since {{5.4.32}} The way I see the problem is that by discarding both {{CollectionChangeWorkUnit}} and {{ModWorkUnit#data}} that contain calculated {{*_MOD}} flags, we are relying on the difference between {{oldState}} and {{newState}}, but debug shows that both states already contain added {{ ListRefIngEntity SetRefIngEntity }}, so comparing those gives us {{false}}. From what I see, {{FlushEntityEvent}} is created with the entities state from {{PersistentContext}} and it differs from what it is in DB. Any ideas on how it might be fixed? ( https://hibernate.atlassian.net/browse/HHH-15480#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15480#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#100206- sha1:3ac329d )

2 years, 6 months

1
0
0 / 0

[JIRA] (HHH-15480) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags

by Artёm Basov (JIRA)

Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZWRiNmU5ZjE5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiZWRiNm... ) HHH-15480 ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiZWRiNm... ) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiZWRiNm... ) Change By: Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) This is, in a sense, a combination of [HHH-7918|https://hibernate.atlassian.net/browse/HHH-7918] and [HHH-7948|https://hibernate.atlassian.net/browse/HHH-7948]. Steps: # Tx1: Create {{ListRefEdEntity}} # Tx2: ## Fetch {{ListRefEdEntity}} created at (1) ## Create and persist {{ListRefIngEntity}} associated with {{ListRefEdEntity}} fetched at (a) ## Change its data , associate with {{ListRefIngEntity}} ## Flush ## Change its data again This will lead to 2nd revision of {{ListRefEdEntity}} with {{reffering_mod=false}} See a [PR|https://github.com/hibernate/hibernate-orm/pull/5253] with a test case. We’ve caught this in {{5.4.32}}, but since test case fails on {{main}}, I’m assuming it affects every version since {{5.4.32}} The way I see the problem is that by discarding both {{CollectionChangeWorkUnit}} and {{ModWorkUnit#data}} that contain calculated {{*_MOD}} flags, we are relying on the difference between {{oldState}} and {{newState}}, but debug shows that both states already contain added {{ListRefIngEntity}}, so comparing those gives us {{false}}. From what I see, {{FlushEntityEvent}} is created with the entities state from {{PersistentContext}} and it differs from what it is in DB. If we can’t rely Any ideas on the difference between the states, I guess our only option is to store {{CollectionChangeWorkUnits}} inside {{ModWorkUnit}} and apply those right before execution. Am I wrong or missing something how it might be fixed ? ( https://hibernate.atlassian.net/browse/HHH-15480#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15480#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#100206- sha1:3ac329d )

2 years, 6 months

1
0
0 / 0

[JIRA] (WEBSITE-631) Broken link: https://hibernate.org/orm/diwbkiads/

by Website Form collector (JIRA)

2 years, 6 months

1
0
0 / 0

[JIRA] (HHH-15480) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags

by Artёm Basov (JIRA)

Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGZkNjhiYmMz... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiNGZkNj... ) HHH-15480 ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiNGZkNj... ) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiNGZkNj... ) Change By: Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) This is, in a sense, a combination of [HHH-7918|https://hibernate.atlassian.net/browse/HHH-7918] and [HHH-7948|https://hibernate.atlassian.net/browse/HHH-7948]. Steps: # Tx1: Create {{ListRefEdEntity}} # Tx2: ## Fetch {{ListRefEdEntity}} created at (1) ## Create and persist {{ListRefIngEntity}} associated with {{ListRefEdEntity}} fetched at (a) ## Change its data , associate with {{ListRefIngEntity}} ## Flush ## Change its data again This will lead to 2nd revision of {{ListRefEdEntity}} with {{reffering_mod=false}} See a [PR|https://github.com/hibernate/hibernate-orm/pull/5253] for with a test case. We’ve caught this in {{5.4.32}}, but since test case fails on {{main}}, I’m assuming it affects every version since {{5.4.32}} The way I see the problem is that by discarding both {{CollectionChangeWorkUnit}} and {{ModWorkUnit#data}} that contain calculated {{*_MOD}} flags, we are relying on the difference between {{oldState}} and {{newState}}, but debug shows that both states already contain added {{ListRefIngEntity}}, so comparing those gives us {{false}}. From what I see, {{FlushEntityEvent}} is created with the entities state from {{PersistentContext}} and it differs from what it is in DB. If we can’t rely on the difference between the states, I guess our only option is to store {{CollectionChangeWorkUnits}} inside {{ModWorkUnit}} and apply those right before execution. Am I wrong or missing something? ( https://hibernate.atlassian.net/browse/HHH-15480#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15480#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#100206- sha1:3ac329d )

2 years, 6 months

1
0
0 / 0

[JIRA] (HHH-15480) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags

by Artёm Basov (JIRA)

Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzRlODFmNTAy... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiYzRlOD... ) HHH-15480 ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiYzRlOD... ) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiYzRlOD... ) Change By: Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) This is, in a sense, a combination of [HHH-7918|https://hibernate.atlassian.net/browse/HHH-7918] and [HHH-7948|https://hibernate.atlassian.net/browse/HHH-7948]. Steps: # Tx1: Create {{ListRefEdEntity}} # Tx2: ## Fetch {{ListRefEdEntity}} created at (1) ## Create and persist {{ListRefIngEntity}} associated with {{ListRefEdEntity}} fetched at (a) ## Change its data , associate with {{ListRefIngEntity}} ## Flush ## Change its data again This will lead to 2nd revision of {{ListRefEdEntity}} with {{reffering_mod=false}} See a [PR|https://github.com/hibernate/hibernate-orm/pull/5253] for a test case. We’ve caught this in {{5.4.32}}, but since test case fails on {{main}}, I’m assuming it affects every version since {{5.4.32}} The way I see the problem is that by discarding both {{CollectionChangeWorkUnit}} and {{ModWorkUnit#data}} that contain calculated {{*_MOD}} flags, we are relying on the difference between {{oldState}} and {{newState}}, but debug shows that both states already contain added {{ListRefIngEntity}}, so comparing those gives us {{false}}. From what I see, {{FlushEntityEvent}} is created with the entities state from {{PersistentContext}} and it differs from what it is in DB. If we can’t rely on the difference between the states, I guess our only option is to store {{CollectionChangeWorkUnits}} inside {{ModWorkUnit}} and apply those right before execution. Am I wrong or missing something? ( https://hibernate.atlassian.net/browse/HHH-15480#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15480#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#100206- sha1:3ac329d )

2 years, 6 months

1
0
0 / 0

[JIRA] (HHH-15480) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags

by Artёm Basov (JIRA)

Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMDQ0M2M0NTVi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiMDQ0M2... ) HHH-15480 ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiMDQ0M2... ) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiMDQ0M2... ) Change By: Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) This is, in a sense, a combination of [HHH-7918|https://hibernate.atlassian.net/browse/HHH-7918] and [HHH-7948|https://hibernate.atlassian.net/browse/HHH-7948]. Steps: # Tx1: Create {{ListRefEdEntity}} # Tx2: ## Fetch {{ListRefEdEntity}} created at (1) ## Create and persist {{ListRefIngEntity}} associated with {{ListRefEdEntity}} fetched at (a) ## Change its data , associate with {{ListRefIngEntity}} ## Flush ## Change its data again This will lead to 2nd revision of {{ListRefEdEntity}} with {{reffering_mod=false}} See a [PR|https://github.com/hibernate/hibernate-orm/pull/5253] for a test case. We’ve caught this in {{5.4.32}}, but since test case fails on {{main}}, I’m assuming it affects every version since {{5.4.32}} The way I see the problem is that by discarding both {{CollectionChangeWorkUnit}} and {{ModWorkUnit#data}} that contain calculated {{*_MOD}} flags, we are relying on the difference between {{oldState}} and {{newState}}, but debug shows that both states already contain added {{ListRefIngEntity}}, so comparing those gives us {{false}}. From what I see, {{FlushEntityEvent}} is created with the entities state from {{PersistentContext}} and it differs from what it is in DB. If we can’t rely on the difference between the states, I guess our only option is to store {{CollectionChangeWorkUnits}} inside {{ModWorkUnit}} and apply those right before execution. Am I missing something? ( https://hibernate.atlassian.net/browse/HHH-15480#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15480#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#100206- sha1:3ac329d )

2 years, 6 months

1
0
0 / 0

[JIRA] (HHH-15480) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags

by Artёm Basov (JIRA)

Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNWEyODMxNjk0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiNWEyOD... ) HHH-15480 ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiNWEyOD... ) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiNWEyOD... ) Change By: Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) This is, in a sense, a combination of [HHH-7918|https://hibernate.atlassian.net/browse/HHH-7918] and [HHH-7948|https://hibernate.atlassian.net/browse/HHH-7948]. Steps: # Tx1: Create {{ListRefEdEntity}} # Tx2: ## Fetch {{ListRefEdEntity}} created at (1) ## Create and persist {{ListRefIngEntity}} associated with {{ListRefEdEntity}} fetched at (a) ## Change its data , associate with {{ListRefIngEntity}} ## Flush ## Change its data again This will lead to 2nd revision of {{ListRefEdEntity}} with {{reffering_mod=false}} See a [PR|https://github.com/hibernate/hibernate-orm/pull/5253] for a test case. We’ve caught this in {{5.4.32}}, but since test case fails on {{ master main }}, I’m assuming it affects every version since {{5.4.32}} The way I see the problem is that by discarding both {{CollectionChangeWorkUnit}} and {{ModWorkUnit#data}} we are relying on the difference between {{oldState}} and {{newState}}, but debug shows that both states already contain added {{ListRefIngEntity}}, so comparing those gives us {{false}}. ( https://hibernate.atlassian.net/browse/HHH-15480#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15480#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#100206- sha1:3ac329d )

2 years, 6 months

1
0
0 / 0

[JIRA] (HHH-15480) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags

by Artёm Basov (JIRA)

Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMjg4ZGEyZjhi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiMjg4ZG... ) HHH-15480 ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiMjg4ZG... ) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiMjg4ZG... ) Change By: Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) This is, in a sense, a combination of [HHH-7918|https://hibernate.atlassian.net/browse/HHH-7918] and [HHH-7948|https://hibernate.atlassian.net/browse/HHH-7948]. Steps: # Tx1: Create {{ListRefEdEntity}} # Tx2: ## Fetch {{ListRefEdEntity}} created at (1) ## Create and persist {{ListRefIngEntity}} associated with {{ListRefEdEntity}} fetched at (a) ## Change its data , associate with {{ListRefIngEntity}} ## Flush ## Change its data again This will lead to 2nd revision of {{ListRefEdEntity}} with {{reffering_mod=false}} See a [PR|https://github.com/hibernate/hibernate-orm/pull/5253] for a test case. We’ve caught this in {{5.4.32}}, but since test case fails on {{master}}, I’m assuming it affects every version since {{5.4.32}} The way I see the problem is that by discarding both {{CollectionChangeWorkUnit}} and {{ModWorkUnit#data}} we are relying on the difference between {{oldState}} and {{newState}}, but debug shows that both states already contain added {{ListRefIngEntity}}, so comparing those gives us {{false}}. ( https://hibernate.atlassian.net/browse/HHH-15480#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15480#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#100206- sha1:3ac329d )

2 years, 6 months

1
0
0 / 0

[JIRA] (HHH-15480) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags

by Artёm Basov (JIRA)

Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiODVjYWQyOTc5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiODVjYW... ) HHH-15480 ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiODVjYW... ) Merging of ModWorkUnit with CollectionChangeWorkUnit followed by another ModWorkUnit leads to lost modified flags ( https://hibernate.atlassian.net/browse/HHH-15480?atlOrigin=eyJpIjoiODVjYW... ) Change By: Artёm Basov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) This is, in a sense, a combination of [ HHH-7918 |https://hibernate.atlassian.net/browse/HHH-7918] and [ HHH-7948 |https://hibernate. atlassian.net/browse/HHH-7948]. Steps: # Tx1: Create {{ListRefEdEntity}} # Tx2: ## Fetch {{ListRefEdEntity}} created at (1) ## Create and persist {{ListRefIngEntity}} associated with {{ListRefEdEntity}} fetched at (a) ## Change its data , associate with {{ListRefIngEntity}} ## Flush ## Change its data again This will lead to 2nd revision of {{ListRefEdEntity}} with {{reffering_mod=false}} See a [PR|https://github.com/hibernate/hibernate-orm/pull/5253] for a test case The way I see the problem is that by discarding both {{CollectionChangeWorkUnit}} and {{ModWorkUnit#data}} we are relying on the difference between {{oldState}} and {{newState}}, but debug shows that both states already contain added {{ListRefIngEntity}}, so comparing those gives us {{false}}. ( https://hibernate.atlassian.net/browse/HHH-15480#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15480#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#100206- sha1:3ac329d )

2 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2022