TiDB auto increment MySQL-compatible behavior clarification (#19861) #19965
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.
This is an automated cherry-pick of #19861
What is changed, added or deleted? (Required)
Improved the MySQL compatibility mode section in auto-increment.md by:
AUTO_ID_CACHE 1
and default modeThese changes make it easier for users to:
Which TiDB version(s) do your changes apply to? (Required)
Since this change includes information about behavior changes across multiple versions (v6.4.0 and v8.1.0) and documents current functionality, it should be applied to:
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?