MySQL Bugs: #98406: socket connection from mysql-workbench fails

Bug #98406	socket connection from mysql-workbench fails
Submitted:	26 Jan 2020 22:59	Modified:	28 Jan 2020 10:57
Reporter:	Christian Hesse (OCA)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	8.0.19	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	mysql-workbench, socket

Description:
MySQL-Workbench 8.0.19 is unable to connect via socket. This broke with mysql-connector-cpp commit "WL13322: Legacy connector support for multi-host".
https://github.com/mysql/mysql-connector-cpp/commit/f234e4b814e406b147d98e5c236a23a41643ff...

How to repeat:
Install MySQL-Workbench 8.0.19, configure to connect to a socket, try to connect.

Suggested fix:
Fix the code.

Hello Christian,

Thank you for the report and feedback.
Observed on Ubuntu 19.10 using mysql-workbench-community(8.0.19-1ubuntu19.10) installed using apt repository. Wrong or unknown protocol error when trying with connection method "Local Socket/Pipe" where as CLI has no issues using same socket file.

-
bin/mysql -uroot -S /tmp/mysql_ushastry.sock
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 6
Server version: 8.0.19 MySQL Community Server - GPL

Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> show variables like 'socket';
+---------------+--------------------------+
| Variable_name | Value                    |
+---------------+--------------------------+
| socket        | /tmp/mysql_ushastry.sock |
+---------------+--------------------------+
1 row in set (0.00 sec)

regards,
Umesh

Screenshot

Attachment: Screenshot from 2020-01-28 04-13-42.png (image/png, text), 107.97 KiB.

Thanks for verification!

However I am not sure moving this to category "MySQL Workbench" is a good idea. You see the issue with workbench, but the actual issue is within connector C++ code (see link to commit above), which is bundled with workbench.

Whatever... I am fine if this gets fixed. ;)

Agree, but since WB affected and hence used WB category. :)
WB dev's can route and coordinate with the appropriate team if required internally.

Sincerely,
Umesh