ensure correct order of sort criteria in mongodb query #172
+128
−3
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
hallettj
commented
Jul 8, 2025
Comment on lines
-56
to
+57
| .collect::<Result<BTreeMap<_, _>>>()?; | ||
| .collect::<Result<IndexMap<_, _>>>()?; // IndexMap preserves insertion order |
There was a problem hiding this comment.
This is the fix - the rest of the PR is testing
codedmart
approved these changes
Jul 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Queries with multiple sort criteria were applying criteria alphabetically in the MongoDB query plan instead of in the order specified in the incoming NDC query.