Docs: Give clearer example of multiple query predicates in one ql file #17277
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
The new names aren't great, so feel free to change them, but I think we do need an explicit example of updating two relations using one ql file.
owen-mc
changed the title
|
Another suggestion for improvement: link to some actual upgrade (and downgrade) scripts, so it's easy to see the kinds of things that people do and how they do them. And perhaps explicitly mention that if you want to create a new table with nothing in it then you don't have to do anything. |
cklin
approved these changes
Sep 11, 2024
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 new names aren't great, so feel free to change them, but I think we do need an explicit example of updating two relations using one ql file.