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
It's currently not possible to annotate a parent entity with @LogicalDelete while its children (hasMany) are without @LogicalDelete. It would be nice to not be forced to mark the entire tree as @LogicalDelete.
Though technically you can physically delete the children by manually issuing delete(physical:true), it would be better to not require any manual intervention. This feature request makes most sense when deletes can cascade (#2).
This limitation seems to be happening becuase of DeleteHibernateFilterConfigurator.enrichLogicalDeleteCollections(). Maybe make the enricher smarter so that it considers if the element type of the collection is marked as @LogicalDelete or not. If not, then don't add filtering for that association.
The text was updated successfully, but these errors were encountered:
It's currently not possible to annotate a parent entity with @LogicalDelete while its children (hasMany) are without @LogicalDelete. It would be nice to not be forced to mark the entire tree as @LogicalDelete.
Though technically you can physically delete the children by manually issuing delete(physical:true), it would be better to not require any manual intervention. This feature request makes most sense when deletes can cascade (#2).
This limitation seems to be happening becuase of DeleteHibernateFilterConfigurator.enrichLogicalDeleteCollections(). Maybe make the enricher smarter so that it considers if the element type of the collection is marked as @LogicalDelete or not. If not, then don't add filtering for that association.
The text was updated successfully, but these errors were encountered: