Do not revalidate encrypted attribute with current encrypted_type #48462
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.
Motivation / Background
Fixes #48445
Fixes #48248
As per the current behaviour, Two queries are being fired to validate uniqueness of an encrypted attribute even in cases when encrypted_type.previous_types is nil. An additional query with the current encrypted/ciphered value should not be fired.
Detail
This PR updates the loop in ExtendedDeterministicUniquenessValidator to iterate over encrypted_type.previous_types only i.e. to exclude the current encrypted_type.
Additional information
For Additional context Please refer to #48445
Checklist
Before submitting the PR make sure the following are checked:
[Fix #issue-number]