Skip to content

Commit

Permalink
dm: add a faq about view in dm faq (#12155) (#13185)
Browse files Browse the repository at this point in the history
  • Loading branch information
ti-chi-bot authored Apr 7, 2023
1 parent cde84c5 commit d08def8
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 0 deletions.
4 changes: 4 additions & 0 deletions dm/dm-faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,10 @@ When you encounter a DDL statement unsupported by TiDB, you need to manually han
>
> Currently, TiDB is not compatible with all the DDL statements that MySQL supports. See [MySQL Compatibility](/mysql-compatibility.md#ddl).
## Does DM replicate view-related DDL statements and DML statements to TiDB?

Currently, DM does not replicate view-related DDL statements to the downstream TiDB cluster, nor does it replicate view-related DML statements to the downstream TiDB cluster.

## How to reset the data migration task?

When an exception occurs during data migration and the data migration task cannot be resumed, you need to reset the task and re-migrate the data:
Expand Down
2 changes: 2 additions & 0 deletions dm/dm-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,8 @@ Before using the DM tool, note the following restrictions:

- DM reports an error when it encounters an incompatible DDL statement. To solve this error, you need to manually handle it using dmctl, either skipping this DDL statement or replacing it with specified DDL statements. For details, see [Skip or replace abnormal SQL statements](/dm/dm-faq.md#how-to-handle-incompatible-ddl-statements).

- DM does not replicate view-related DDL statements and DML statements to the downstream TiDB cluster. It is recommended that you create the view in the downstream TiDB cluster manually.

+ GBK character set compatibility

- DM does not support migrating `charset=GBK` tables to TiDB clusters earlier than v5.4.0.
Expand Down

0 comments on commit d08def8

Please sign in to comment.