Issue with DM Full Data Synchronization Not Inheriting Source Character Set

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: dm全量同步无法继承source字符集问题

| username: Hacker007

To solve the case insensitivity issue, we have now set up a new cluster and initialized it with case insensitivity support. However, when configuring the DM task and adding the collation_compatible: strict parameter, we found that newly created databases and tables can inherit MySQL’s character set and collation rules, but existing databases and tables do not inherit MySQL’s character set and still use the default character set after synchronization. How can this be resolved?

2
| username: Hacker007 | Original post link

Or is there any command or statement to globally modify the character set of the database, table, or field?

3
| username: Tank001 | Original post link

Is the version too low? Have you upgraded it?

4
| username: Z六月星星 | Original post link

Resynchronize the old table once, or modify the character set of the database and table. The global setting only sets the default, and it seems that there is no unified modification.

5
| username: system | Original post link

This topic was automatically closed 1 minute after the last reply. No new replies are allowed.