Case insensitive Constraints via IgnoreCase annotation #1005
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.
Option 1 for case insensitive Constraints:
Give the repository method author an
@IgnoreCase
annotation with which to indicate when a Constraint should be applied independent of case. Typically it will be known upfront that the database contains a mixture of case, and it will be more convenient to specify this information in a single place on the repository method signature rather than everywhere it is used (where there is also the risk of forgetting to do it in one place).Example usage:
We should choose between this PR or #1006 (or if someone thinks of another way) for case-insensitive constraints