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

Backport-12.0: Take MySQL Column Type Into Account in VStreamer #9355

Merged
merged 2 commits into from Dec 10, 2021

Conversation

mattlord
Copy link
Contributor

@mattlord mattlord commented Dec 10, 2021

Description

This is a backport of #9331. Please see details there.

Related Issue(s)

Checklist

  • Should this PR be backported? NO
  • Tests were added
  • Documentation is not required

This is required when we need to match MySQL behavior for data
that requires column type information as well. For example, the
binlog event metadata makes no distinction between events for a
BINARY(4) column and events for a CHAR(4) column with a binary
collation like utf8mb4_bin. So we need to know the underlying
MySQL column type in order to handle them disctinctly -- MySQL
pads (fixed length) binary columns on the right side with null
bytes, but it does NOT do that for (fixed lengthed) CHARo
columns, regardless of the collation.

Signed-off-by: Matt Lord <mattalord@gmail.com>
And use ToLower when looking for BINARY types to be safe.

Signed-off-by: Matt Lord <mattalord@gmail.com>
@deepthi deepthi merged commit a7b2cb4 into release-12.0 Dec 10, 2021
@deepthi deepthi deleted the Backport_9331_12.0 branch December 10, 2021 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants