fix(db-mongodb): handle admin.condition in sparse unique indexes#1
Merged
Conversation
rachit367
force-pushed
the
fix-conditional-sparse-index
branch
from
8c944c8 to
09c9f40
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What?
Fixes an issue where conditionally required unique fields created non-sparse MongoDB indexes.
Why?
Fields using
admin.conditioncan be optional at runtime, but the current logic only checks the staticrequiredproperty.This causes duplicate key errors when multiple documents contain
nullvalues.How?
Updated sparse index logic in
buildSchema.tsto account foradmin.condition.Fixes payloadcms#16298