feat: EXPOSED-403 Implement EntityClass.restriction
- a means of providing soft deletes
#2114
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is my attempt at showcasing/drafting a version of "DAO restrictions", similarly to how
@SQLRestriction
works in Hibernate (which can be used for soft deletes), but without the magic annotation setup.Youtrack: https://youtrack.jetbrains.com/newIssue?project=EXPOSED&draftId=25-5413167
Usage:
Why "restriction"?
AND <restriction>
fashion, in my mind