RFC 1024: Index ordering #83
Open
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
Provide a way to specify ordering for the index expressions. Also make the support of indexes on multiple fields more consistent (stop using tuples for that).
elprans
reviewed
Aug 9, 2023
| ======================= | ||
|
|
||
| This change is *syntactically* backwards compatible since all of the extra | ||
| specification for the index are optional. However, sematically, we should not |
Member
There was a problem hiding this comment.
I don't think purity is worth the cost of breaking compatibility and requiring a migration. IMO we should continue to special-case tuples.
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.
Provide a way to specify ordering for the index expressions. Also make the support of indexes on multiple fields more consistent (stop using tuples for that).