Skip to content

UUID vs binary(16) #1034

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.

Sign up for GitHub

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

Jump to bottom
Closed
ghost opened this issue Nov 21, 2022 · 2 comments
Closed

UUID vs binary(16) #1034

ghost opened this issue Nov 21, 2022 · 2 comments
Milestone
4.23.04.0

Comments

@ghost
Copy link

ghost commented Nov 21, 2022 •
edited by ghost
Loading

对于dtle.gtid_executed表中的source_uuid binary(16), 在binlog中以string类型表达

columntype 254 MYSQL_TYPE_STRING

binlog储存binary时, 会忽略结尾的0.
@ghost
Copy link
Author

ghost commented Nov 21, 2022

The use of CHARACTER SET binary in the definition of a CHAR, VARCHAR, or TEXT column causes the column to be treated as a binary data type. For example, the following pairs of definitions are equivalent:

CHAR(10) CHARACTER SET binary
BINARY(10)

VARCHAR(10) CHARACTER SET binary
VARBINARY(10)

TEXT CHARACTER SET binary
BLOB

@ghost
Copy link
Author

ghost commented Nov 24, 2022

https://github.com/go-mysql-org/go-mysql/issues/ 477

ghost pushed a commit that referenced this issue Nov 24, 2022
handle MySQL server UUID with trailing zeros #1034
7a98826
@ghost ghost added this to the 4.22.12.0 milestone Nov 24, 2022
@ghost ghost closed this as completed Nov 24, 2022
ghost pushed a commit that referenced this issue Nov 28, 2022
handle MySQL server UUID with trailing zeros #1034
09b64c4
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
4.23.04.0
Development

No branches or pull requests
0 participants