[MXS-1927] Binlogrouter always uses binary collation for results Created: 2018-06-15  Updated: 2019-09-04  Resolved: 2019-09-04

Status: Closed
Project: MariaDB MaxScale
Component/s: binlogrouter
Affects Version/s: 2.2.13
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: markus makela Assignee: Unassigned
Resolution: Won't Fix Votes: 1
Labels: None


 Description   

For example the output of SHOW SLAVE STATUS always uses the binary collation. This is not what the MariaDB server returns.



 Comments   
Comment by Alex Boag-Munroe [ 2018-09-13 ]

As per the expected behaviour when connecting to a MySQL/MariaDB instance, the client's character set should be used when returning query/command results rather than a hard coded override as this results in unexpected behaviour and errors with some clients (Some DBAPI client libraries for python, for example).

Comment by Johan Wikman [ 2019-09-04 ]

Will be fixed in the binlog router to be released in 2.5.

Generated at Thu Feb 08 04:10:26 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.