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>

Commits

Commits on Nov 3, 2019

mysql: handle db name correctly