*: clarify unsupported behavior in generated column #2262
Merged
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
djshow832
reviewed
Feb 20, 2020
Co-Authored-By: TomShawn <41534398+TomShawn@users.noreply.github.com>
TomShawn
added
the
status/can-merge
|
/run-all-tests |
This was referenced Mar 11, 2020
TomShawn
added
translation/done
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.
What is changed, added or deleted?
We fix logs of bugs related to
generated columnin TiDB v4.0, for the known unsupported behavior in v4.0 and previous versions, we should update the docs.What is the related PR or file link(s)?
Reference link(s):
This PR is to align with:
ALTER TABLEtidb#10758defaultinto generated columns tidb#11901DEFAULTinON DUPLICATE KEY UPDATEstatement tidb#13168N/A (not applicable)
Which TiDB version(s) does your changes apply to?
Note: If your changes apply to multiple TiDB versions, make sure you update the documents in the corresponding version folders such as "dev", "v3.0", "v2.1" and "v3.1" in this PR.