Bug #102959 MySQL Workbench Unable to Connect to Vitess DB Proxy
Submitted: 12 Mar 20:16 Modified: 18 Mar 16:34
Reporter: Allen Kenney Email Updates:
Status: Open Impact on me:
None 
Category:MySQL Workbench Severity:S4 (Feature request)
Version:8.0.23 OS:Microsoft Windows (Microsoft Windows 10 Pro)
Assigned to: CPU Architecture:Any
Tags: Vitess, WBBugReporter

[12 Mar 20:16] Allen Kenney
Description:
My company is migrating our database to sit behind a DB proxy called Vitess (https://vitess.io/). Vitess is used by several large companies to split their DB into many DBs and then hide the complexity of all the different databases behind a single proxy/routing layer.

I cannot connect to MySQL Workbench to the Vitess "DB". I can connect via JDBC and with other tools such as DBeaver or SequelPro, but I would REALLY like to keep using MySQL Workbench.

I found a discussion thread of other people with the same error here: https://stackoverflow.com/questions/61125460/issue-with-connecting-vitess-from-mysql-work-...

How to repeat:
Setup a Vitess DB proxy and then try to connect to it with MySQL Workbench

This error is displayed:
[ERR][SQL Editor Form]: SQL editor could not be connected: syntax error at position 20 near 'current_user'

Suggested fix:
Update MySQL Workbench so that it can connect to Vitess (https://vitess.io/)
[18 Mar 16:34] Allen Kenney
Vitess has a fix for this bug. (Still need to verify the fix myself.)
https://github.com/vitessio/vitess/issues/7697
https://github.com/vitessio/vitess/pull/7705