Skip to content
This repository has been archived by the owner on Jan 3, 2025. It is now read-only.

Add handle-failed-sql-statements.md #273

Merged
merged 9 commits into from
Aug 21, 2020
Merged
2 changes: 1 addition & 1 deletion en/TOC.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@
- [Pause a Task](pause-task.md)
- [Resume a Task](resume-task.md)
- [Stop a Task](stop-task.md)
- [Skip or Replace Abnormal SQL Statements](skip-or-replace-abnormal-sql-statements.md)
- [Handle Failed SQL Statements](handle-failed-sql-statements.md)
- [Manually Handle Sharding DDL Locks](feature-manually-handling-sharding-ddl-locks.md)
- [Manage Table Schema during Migration](manage-schema.md)
- [Handle Alerts](handle-alerts.md)
Expand Down
2 changes: 1 addition & 1 deletion en/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ DM will attempt to split a single statement containing multiple DDL change opera

## How to handle incompatible DDL statements?

When you encounter a DDL statement unsupported by TiDB, you need to manually handle it using dmctl (skipping the DDL statement or replacing the DDL statement with a specified DDL statement). For details, see [Skip or replace abnormal SQL statements](skip-or-replace-abnormal-sql-statements.md).
When you encounter a DDL statement unsupported by TiDB, you need to manually handle it using dmctl (skipping the DDL statement or replacing the DDL statement with a specified DDL statement). For details, see [Handle failed SQL statements](handle-failed-sql-statements.md).

> **Note:**
>
Expand Down
Loading