handle entry sorting in mongo #772
Merged
Conversation
This file contains 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
|
See #771 (comment) I feel like this is a good intermediate solution to the performance problems, however users will want to be able to sort their minority language correctly using customized rules, and I don't believe we can teach the database to sort based on custom rules. So the ultimate implementation will need to be done either client side (load all data) or server side (memory intensive) |
myieye
approved these changes
May 2, 2024
Co-authored-by: Tim Haasdyk <myieye@gmail.com>
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.
closes #771
you can't select in a sort aggreigate, so that's why I needed to select a new field first in order to sort by it.