Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Logically delete parent but physically delete children #6

Open
vahidpaz opened this issue Feb 26, 2014 · 0 comments
Open

Comments

@vahidpaz
Copy link

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.

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

No branches or pull requests

1 participant