Shardingsphere-proxyuses a DBeaver connection and cannot update data

hehua2018 commented 2 years ago

Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

Searched open and closed GitHub issues.
Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Which version of ShardingSphere did you use?

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

Expected behavior

Actual behavior

Reason analyze (If you can)

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

Example codes for reproduce this issue (such as a github link).

Shardingsphere-proxy 5.1.2 uses the DBeaver connection, but the data in the table cannot be updated

RaigorJiang commented 2 years ago

HI @hehua2018 Thanks for your feedback.

To answer your question, we need to investigate what SQL statement DBeaver sends to the Proxy. Can you provide the specific version information of DBeaver so that we can reproduce the problem.

hehua2018 commented 2 years ago

DBeaver version 22.1.1.202206261508

terrymanu commented 2 years ago

What kind of database and version do you use?

TeslaCN commented 2 years ago

I found something when I using DBeaver. https://github.com/apache/shardingsphere/issues/19405

TeslaCN commented 2 years ago

This is because DBeaver fetch meta data from information_schema, which is not supported by ShardingSphere-Proxy for now.

There are many errors about information_schema when connecting ShardingSphere-Proxy by DBeaver.

github-actions[bot] commented 1 year ago

Hello , this issue has not received a reply for several days. This issue is supposed to be closed.

apache / shardingsphere