January 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HBX-2478) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_6_2 to version 6.2.0.CR2

by Koen Aers (JIRA)

1 year, 4 months

1
0
0 / 0

[JIRA] (HHH-15512) Querying for an entity persisted but not flushed to the database causes the exception 'A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance'

by Christoph Watzl (JIRA)

Christoph Watzl ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15512 ( https://hibernate.atlassian.net/browse/HHH-15512?atlOrigin=eyJpIjoiOGM0OD... ) Re: Querying for an entity persisted but not flushed to the database causes the exception 'A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance' ( https://hibernate.atlassian.net/browse/HHH-15512?atlOrigin=eyJpIjoiOGM0OD... ) @Andrea Boriero I opened a new issue with a test case: https://hibernate.atlassian.net/browse/HHH-16117 ( https://hibernate.atlassian.net/browse/HHH-16117 ) Turned out it is a different issue, even though the symptoms are quite similar. It appears to be related to Embeddables. ( https://hibernate.atlassian.net/browse/HHH-15512#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15512#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#100214- sha1:d3cc1a2 )

1 year, 4 months

1
0
0 / 0

[JIRA] (HBX-2478) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_6_2 to version 6.2.0.CR2

by Koen Aers (JIRA)

1 year, 4 months

1
0
0 / 0

[JIRA] (HHH-11936) Stabilize "empty composites" feature

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-11936 ( https://hibernate.atlassian.net/browse/HHH-11936?atlOrigin=eyJpIjoiMDhkMT... ) Re: Stabilize "empty composites" feature ( https://hibernate.atlassian.net/browse/HHH-11936?atlOrigin=eyJpIjoiMDhkMT... ) > > > > What it can’t possibly be is a global setting. A MonetaryAmount with all > null fields is never a meaningful monetary value no matter what “global” > characteristics your program has. And indeed it seems to me that the > default behavior is always better and more correct for at least the > majority of embeddable classes in a program > > I suppose it makes sense. We’d need an alternative before we remove the global setting though, because people do rely on this feature. > > > > I mean, TBH, I really struggle to come up with even a single legit usecase > for a class with everything null, and nobody so far has ever been able to > show me one. For every concrete example I can think of, the default > behavior is more correct. Perhaps you have a convincing example that would > help me understand the motivation for this? I admit that I sometimes fall > short on imagination. Even if you can think of an couple of great > motivating cases, I still insist that such cases will always be exceptional > cases in every program. > > I’ve seen business applications where embeddables where used to group together information within an entity that have a common theme. So let’s say in a Customer entity you’d have a ShippingSection , a LegalSection , etc. All those sections being, well, just ways to group information together in a more manageable fashion than just dropping everything at the root of the entity. And that structure does help developers when manipulating the entity throughout the application, especially when the IDE auto-completes your calls to getters. In that situation, a null “section” simply doesn’t make sense, and more importantly, it’s just inconvenient. You would have to check for nullness every time you call getShippingSection().setAddress("foo") , and manually set the embeddable to a non-null value. Or you’d have to write your getters in such a way that they automatically detect null embeddeds and initialize them with non-empty values. Sure, in some cases those “sections” could be separate entities with a @OneToOne association, but in the cases I encountered, that had to practical benefit and implied a slightly more complicated DB schema, so we decided against it. ( https://hibernate.atlassian.net/browse/HHH-11936#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-11936#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#100214- sha1:d3cc1a2 )

1 year, 4 months

1
0
0 / 0

[JIRA] (HBX-2477) Update version identifier to 6.2.0.CR2

by Koen Aers (JIRA)

1 year, 4 months

1
0
0 / 0

[JIRA] (HHH-16117) Querying entity with collection in Embeddable causes 'A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance'

by Christoph Watzl (JIRA)

Christoph Watzl ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTVmZmRkMjM3... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16117?atlOrigin=eyJpIjoiNTVmZm... ) HHH-16117 ( https://hibernate.atlassian.net/browse/HHH-16117?atlOrigin=eyJpIjoiNTVmZm... ) Querying entity with collection in Embeddable causes 'A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance' ( https://hibernate.atlassian.net/browse/HHH-16117?atlOrigin=eyJpIjoiNTVmZm... ) Change By: Christoph Watzl ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Steps to reproduce: * Entity hierarchy: ** Entity A <<has a>> Embeddable B ** Embeddable B <<has many, cascade=all-delete-orphan>> Entity C * Persist an instance of A with an instance of B and non-empty collection of C * *Do NOT flush the session* * Query for A with HQL query Result: {noformat}org.hibernate.HibernateException: A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance: org.hibernate.bugs.hhh16117.model.Parent.data.children{noformat} Workaround: Explicitly flush() after persist() Reproducer: [https://github.com/cwatzl/HHH-16117|https://github.com/cwatzl/HHH-16117] Similar symptoms to [HHH-15512|https://hibernate.atlassian.net/browse/HHH-15512], but seems to be related to Embeddables. May also possibly be related to [ Detailed description & reproducer coming within the hour HHH-15864|https://hibernate.atlassian.net/browse/HHH-15864 ]. ( https://hibernate.atlassian.net/browse/HHH-16117#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16117#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#100214- sha1:d3cc1a2 )

1 year, 4 months

1
0
0 / 0

[JIRA] (HHH-15665) Mariadb is missing identifier quote on SEQUENCE QUERY

by Jan Schatteman (JIRA)

1 year, 4 months

1
0
0 / 0

[JIRA] (HBX-2477) Update version identifier to 6.2.0.CR2

by Koen Aers (JIRA)

1 year, 4 months

1
0
0 / 0

[JIRA] (HBX-2477) Update version identifier to 6.2.0.CR2

by Koen Aers (JIRA)

1 year, 4 months

1
0
0 / 0

[JIRA] (HBX-2477) Update version identifier to 6.2.0.CR2

by Koen Aers (JIRA)

1 year, 4 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 January 2023