We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
bug
synchronization did not effect
The source library and the target library have a table field as follows
# Original `bank_card_number` varchar(30) COLLATE utf8mb4_general_ci NOT NULL DEFAULT '' COMMENT '银行卡号', # target `bank_card_number` varchar(30) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL DEFAULT '' COMMENT '银行卡号',
The main difference is that the target table specifies the CHARACTER SET utf8mb4.
Then when using the library table synchronization, there is a difference, ddl is as follows (which is correct)
ALTER TABLE `admin_owners` MODIFY COLUMN `bank_card_number` varchar(30) COLLATE utf8mb4_general_ci NOT NULL DEFAULT '' COMMENT '银行卡号';
Then generate the ticket, execute successfully.
However, when you synchronize the library table again, you will find that there is still a difference, and then the above,
zero difference
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Provide the Bytebase version you are using
bug
Describe the bug
synchronization did not effect
Steps to reproduce
The source library and the target library have a table field as follows
The main difference is that the target table specifies the CHARACTER SET utf8mb4.
Then when using the library table synchronization, there is a difference, ddl is as follows (which is correct)
Then generate the ticket, execute successfully.
However, when you synchronize the library table again, you will find that there is still a difference, and then the above,
Expected behavior
zero difference
Provide the database you are using
No response
Provide the version control system you are using
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: