Document using a fragment with order_by/3 #2271
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
|
❤️ 💚 💙 💛 💜 |
bartekupartek
pushed a commit
to bartekupartek/ecto
that referenced
this pull request
Mar 19, 2019
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.
The documentation didn't show that a fragment could be used with
order_by/3, so I added my own use case.Is it too weird? The idea is to have an order that's shuffled but stable for pagination (in the case where I'm using it, inserting and deleting records is fairly rare; such changes would change the ordering some because a new record might appear in the middle of the result set.)
The point is not to show this particular use case, it's just the example I have for why fragments might be needed.