Add MERGE to SQL support documentation#13548
Merged
martint merged 1 commit intotrinodb:masterfrom Aug 17, 2022
Merged
Conversation
colebow
approved these changes
Aug 8, 2022
jhlodin
force-pushed
the
jl/sql-merge-connectors
branch
from
50cc7d6 to
4cfb837
Compare
Member
|
So odd how this was implemented in the object storage connectors and kudu .. |
mosabua
approved these changes
Aug 15, 2022
Member
mosabua
left a comment
mosabua
left a comment
There was a problem hiding this comment.
We should make sure this gets in before the 393 release since that ships the merge command and without this PR the documentation will be misleading
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
5 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
Add links to the new SQL MERGE statement to the appropriate documentation
Improvement
Documentation
Document which connectors support SQL MERGE
Related issues, pull requests, and links
Documentation
( ) No documentation is needed.
(x) 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
(x) No release notes entries required.
( ) Release notes entries required with the following suggested text: