don't throw error when comparing options with/without collation #9224
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.
Thanks for submitting a pull request! Please provide enough information so that others can review your pull request. The two fields below are mandatory.
If you're making a change to documentation, do not modify a
.html
file directly. Instead find the corresponding.pug
file or test case in thetest/docs
directory.Summary
On a collection, and in the schema, have an index with and without a collation. Run
syncIndexes()
, it fails at line 21 withTypeError: Cannot convert undefined or null to object
whenkey
is "collation" butoptions.collation
is undefined.Examples
Example arguments to isIndexesEqual that throw an error: