Skip to content

Conversation

@marko-bekhta
Copy link
Member

https://hibernate.atlassian.net/browse/HSEARCH-5517


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.


@marko-bekhta marko-bekhta force-pushed the fix/HSEARCH-5517-Document-is-updated-instead-of-deleted-on-cascading-delete-in-OneToOne-relations branch from a7668c3 to 2e1f0c0 Compare November 10, 2025 13:28
@JoinColumn(name = "PARENT_ID_CUSTOM_NAME")
@OneToOne
@IndexedEmbedded
@AssociationInverseSide(inversePath = @ObjectPath(@PropertyValue(propertyName = "cascadableChildMapsId")))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This shouldn't be necessary, there's already a mappedBy on the other side?

Comment on lines 118 to 120
CascadableChildMapsId child = session.find( CascadableChildMapsId.class, 1L );
child.setName( "to-be-deleted" );
session.persist( child );
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This call to persist is strange, as the entity is already persisted?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh yeah, missed it when cleaning up the reproducer, 👍🏻

@marko-bekhta
Copy link
Member Author

By the way, this makes me wonder... Can't you reproduce this without cascades? Just be removing both the parent and child explicitly?

I don't think so ... if we start removing things explicitly without cascading, then ORM would force us to set nulls or we'll get Hibernate ORM exceptions about those dangling objects ... (I think we already have tests for that scenario in place)...

handle an edge case

yeah... I only could get it to "fail" with this mapping, removing any other part of what's in was leading to a different oreder of remove events and all was "ok" in a sense that update was planned first but then the remove event from ORM came in and the final plan was correct ... 😖

@marko-bekhta marko-bekhta force-pushed the fix/HSEARCH-5517-Document-is-updated-instead-of-deleted-on-cascading-delete-in-OneToOne-relations branch from 2e1f0c0 to 4ebe234 Compare November 11, 2025 17:50
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants