Open
Conversation
Member
Author
|
|
nilmerg
force-pushed
the
fix/unstable-service-order
branch
from
c561ad0 to
5f63502
Compare
Member
Author
|
We'll need to verify query plans of several backends and versions in order to make sure this has no disadvantages. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Services usually have similar (if not equal) names across different hosts. Sorting such after (display_)name, might result in unexpected results depending on the used database backend.
To guarantee a deterministic order we have to use more than a single column if said column isn't variant enough.