You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VisitCollectionsBeforeSave must be called no matter if substitute is already true.
On versioned entities this is always the case.
fredericDelaporte
changed the title
Cascading orphan delete does not work in corner case on versioned entity
Cascading orphan delete may not work on versioned entity
Jun 19, 2023
VisitCollectionsBeforeSave must be called no matter if substitute is already true.
On versioned entities this is always the case.
Fixes#3325
Co-authored-by: Alex Zaytsev <hazzik@gmail.com>
Co-authored-by: Roman Artiukhin <bahusdrive@gmail.com>
In a certain scenario, the orphan delete of a child entity is not performed:
Parent entity must be versioned.
Way to reproduce
Child is then added to the database with NULL as Parent pointer.
Pull request is created.
I would appreciate addition to next 5.4.x release.
The text was updated successfully, but these errors were encountered: