Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

when use "strict" collation compatibility, DM syncer may generate unexpected ddl #6832

Closed
lance6716 opened this issue Aug 22, 2022 · 0 comments · Fixed by #6833
Closed

when use "strict" collation compatibility, DM syncer may generate unexpected ddl #6832

lance6716 opened this issue Aug 22, 2022 · 0 comments · Fixed by #6833
Labels
affects-6.1 area/dm Issues or PRs related to DM. severity/moderate This is a moderate bug. type/bug This is a bug.

Comments

@lance6716
Copy link
Contributor

What did you do?

like pingcap/tidb#37241

"create table `test`.`t1` (name varchar(20) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin)",

will become

"CREATE TABLE `test`.`t` (`name` VARCHAR(20) CHARACTER SET UTF8MB4 COLLATE utf8mb4_general_ci COLLATE utf8mb4_bin)",

What did you expect to see?

No response

What did you see instead?

No response

Versions of the cluster

master

current status of DM cluster (execute query-status <task-name> in dmctl)

(paste current status of DM cluster here)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.1 area/dm Issues or PRs related to DM. severity/moderate This is a moderate bug. type/bug This is a bug.
Development

Successfully merging a pull request may close this issue.

1 participant