Fix query options bug from Mongodb breaking change #615
Conversation
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
dozoisch
approved these changes
Oct 5, 2020
Collaborator
|
Thanks! |
Mamoona-Ghania
pushed a commit
to FaizaAslam013/Devops-Mids-Exam
that referenced
this pull request
Dec 13, 2025
Fix query options bug from Mongodb breaking change
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The PR: #558 updated mongodb version from
2.2.24to3.5.5. There are some breaking changes in mongodb 3.x.x version like find which removed the projection field as separate parameters and expectes it in options.Since projection was the second field and query_options was the third one, all features like sorting and pagination were corrupted by the update. This PR will fix this issue.