-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot connect to Shardingsphere-Proxy with MySQL Workbench #11762
Comments
This question has been consulted. I also have this problem when testing the version of navicat12. You can log in normally by using navicat11. |
@cqiwencom Hi, i'm currently using MySQL Workbench 8.0.26 and I can't use Navicat because I don't have a license. |
@sgc109 Hi thanks for your detailed report. It is an important and complex issue to adapt different clients. |
Hi @sgc109 @cqiwencom |
@RaigorJiang Thanks, let firstly check out all the relevant issues and do some tests. Next, we can make a plan with some hints we got. |
Yes, it should be like this. |
Hi guys, @sgc109 @cqiwencom As for the tables information in the Workbench, it needs to query the P.S. I tested the following clients:
|
Look forward to this feature. ;-) |
The connection problem has been resolved, this issue will be closed. |
Bug Report
Which version of ShardingSphere did you use?
5.0.0-beta
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
Shardingsphere-Proxy
Expected behavior
Being able to connect to Sharindgsphere-Proxy.
Actual behavior
Test Connection
button,Reason analyze (If you can)
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
JDK version
9
MySQL Workbench version
8.0.26
stdout.log
after the proxy successes to startIt works when I try to access MySQL CLI client as follows , but doesn't work when I connect with MySQL Workbench.
![Screen Shot 2021-08-11 at 5 59 11 PM](https://user-images.githubusercontent.com/7943694/129000822-24feac42-1e98-431b-86da-002f5f5593ab.png)
Example codes for reproduce this issue (such as a github link).
https://github.com/sgc109/shardingsphere-proxy-bin
The text was updated successfully, but these errors were encountered: