sql-statement: update sql-statement-change-column
What is changed, added or deleted? (Required)
- Update the format of usage section: add more description about SQL statements, remove "Query OK", and move some examples to "Compatibility with MySQL"
- Update the limitation of "ERROR 1105 (HY000): can't run multi schema change". In TiDB v5.0, tidb_enable_change_multi_schema is introduced to run multiple schema change and TiDB v6.2.0 supports multiple schema change by default.
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
- [x] master (the latest development version)
What is the related PR or file link(s)?
- This PR is translated from:
- Other reference link(s):
looks so strange...

[REVIEW NOTIFICATION]
This pull request has been approved by:
- Oreoxmt
To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.
The full list of commands accepted by this bot can be found here.
Reviewer can indicate their review by submitting an approval review. Reviewer can cancel approval by submitting a request changes review.
/status LGT1
Removed the needs-cherry-pick-release-7.0 label because the v7.0 docs have been archived at https://docs-archive.pingcap.com/zh/tidb/v7.0 and will no longer receive new updates.
Removed the needs-cherry-pick-release-7.2 label because the v7.2 docs have been archived at https://docs-archive.pingcap.com/zh/tidb/v7.2 and will no longer receive new updates.
PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.