sql-statements: say that optimistic constraint checks are deferred until the transaction is committed

[yahonda]

What is changed, added, or deleted? (Required)

In sql-statements/sql-statement-commit.md, the MySQL compatibility section says that with optimistic locking, UNIQUE and PRIMARY KEY constraint checks "are deferred until statement commit". The checks are deferred until the transaction commits, which is why the COMMIT statement can fail. The same behavior is described that way elsewhere:

• constraints.md: "the unique check was deferred until the transaction is committed".
• transaction-overview.md: "These checks are instead performed on transaction COMMIT".

This PR changes "until statement commit" to "until the transaction is committed". It was flagged by CodeRabbit on the Japanese translation PR #24017, which inherited it from EN.

Which TiDB version(s) do your changes apply to? (Required)

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)

What is the related PR or file link(s)?

• Related code change PR links (if applicable): N/A
• This PR is translated from: N/A
• Other reference link(s): i18n(ja): fix translation defects in sql-statements docs (alter-table-compact to create-table-like) #24017

AI agent involvement

• The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

Next included review available in 32 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Repository: pingcap/docs/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: a0682d18-3b7c-4d60-bb83-7679f34bd185

📥 Commits

Reviewing files that changed from the base of the PR and between 2ea1beb and 2c52713.

📒 Files selected for processing (1)

• sql-statements/sql-statement-commit.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[qiancai]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-09-30 00:47:57.738972461 +0000 UTC m=+757002.964193568: ☑️ agreed by qiancai.

[qiancai]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [qiancai]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.5: #24064.