mysql: handle db name correctly#5398
Merged
sougou merged 1 commit intovitessio:masterfrom Nov 3, 2019
Merged
Conversation
Fixes vitessio#5206 The conn schemaname var can get set through a new connection or a ComInitDB packet. However, a use statement bypasses this mechanism and gets handled at the vtgate level. This causes problems because schemaName in the connection disagrees with TargetString in vtgate. To fix this, the new scheme calls a new handler function: ComInitDB every time schemaName is initialized or changed in the connection. This way, the TargetString remains the authoritative source for the current db name. I couldn't write a test for this specific behavior change because the mysql go client does not implement support for ComInitDB. But I've verified the things generally work as expected. Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Contributor
|
I managed to manually verify this as fixed, by using local example. Here is the previous behavior: Here is the new behavior: |
Contributor
|
@sougou LGTM except the resharding_rbr test is failing. Did you want to bump the CI? |
deepthi
approved these changes
Nov 3, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #5206
The conn schemaname var can get set through a new connection
or a ComInitDB packet. However, a use statement bypasses this
mechanism and gets handled at the vtgate level. This causes
problems because schemaName in the connection disagrees with
TargetString in vtgate.
To fix this, the new scheme calls a new handler function: ComInitDB
every time schemaName is initialized or changed in the connection.
This way, the TargetString remains the authoritative source
for the current db name.
I couldn't write a test for this specific behavior change because
the mysql go client does not implement support for ComInitDB.
But I've verified the things generally work as expected.
Signed-off-by: Sugu Sougoumarane ssougou@gmail.com