Clarify use of expressions in UPDATE docs#12438
Merged
electrum merged 1 commit intotrinodb:masterfrom May 20, 2022
Merged
Conversation
mosabua
requested changes
May 17, 2022
colebow
force-pushed
the
colebow/update-docs
branch
from
543a69a to
aa3cc3e
Compare
colebow
force-pushed
the
colebow/update-docs
branch
from
aa3cc3e to
26b1f59
Compare
electrum
approved these changes
May 20, 2022
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
3 participants
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.
Description
This formats the two examples for update, adds a function call to the second, and adds a third example to make it clear how Trino supports using expressions (including functions and subqueries) as the predicate for an UPDATE statement.
Improvement
Docs
Documentation
( ) No documentation is needed.
(✅) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
(✅) No release notes entries required.
( ) Release notes entries required with the following suggested text: