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

MYSQL_TYPE_VAR_STRING handling in binlog protocol #151

Open
megatron10 opened this issue Sep 1, 2024 · 0 comments
Open

MYSQL_TYPE_VAR_STRING handling in binlog protocol #151

megatron10 opened this issue Sep 1, 2024 · 0 comments

Comments

@megatron10
Copy link

As per Mysql code bsae comments/docs MYSQL_TYPE_VAR_STRING can be used for both Strings and Enum types. The connector code has special handling for checking if MYSQL_TYPE_STRING is actually an Enum instead, but there is no such handling for MYSQL_TYPE_VAR_STRING.

Mysql codebase reference point:
https://github.com/mysql/mysql-server/blob/596f0d238489a9cf9f43ce1ff905984f58d227b6/libs/mysql/binlog/event/rows_event.h#L371

Connector code base type code handling:
https://github.com/osheroff/mysql-binlog-connector-java/blob/master/src/main/java/com/github/shyiko/mysql/binlog/event/deserialization/AbstractRowsEventDataDeserializer.java#L126

An underlying Enum column with MYSQL_TYPE_VAR_STRING type in the table map will be treated as string, when infact its an Enum.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant