release-2.1: sql: fix the evaluation of CHECK after ON CONFLICT DO UPDATE SET #32780
Conversation
This file contains 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
|
This change is |
Release note (bug fix): CockroachDB now properly evaluates CHECK constraints after a row conflict in INSERT ON CONFLICT, when the CHECK constraint depends on a column not assigned by DO UPDATE SET.
knz
force-pushed
the
backport2.1-32779
branch
from
e2bb89e
to
447d47d
Compare
bobvawter
approved these changes
Dec 3, 2018
There was a problem hiding this comment.
Reviewed 2 of 2 files at r1.
Reviewable status:complete! 0 of 0 LGTMs obtained
knz
moved this from Triage
to Current milestone
in (DEPRECATED) SQL Front-end, Lang & Semantics
knz
moved this from Current milestone
to Finished (m2.2-2)
in (DEPRECATED) SQL Front-end, Lang & Semantics
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.
Backport 1/1 commits from #32779.
/cc @cockroachdb/release