-
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
information_schema and sys relevant SQLs can't parse or route #6693
Comments
Hibernate 5.4 + ShardingSphere JDBC 5.0.0-RC1-SNAPSHOT + PostgreSQL 12, has similar exception: Hibernate settings:
SQL executed by hibernate automatically: |
The exception caused by parse and route procedure. @tristaZero , can you have a look? |
any update? |
Mysql has same problem here. |
Hi thanks for your attention. |
org.apache.shardingsphere.sharding.route.engine.type.unconfigured.ShardingUnconfiguredTablesRoutingEngine#findDataSourceName entry.getValue() tablenames is upcase but logicTables is lowercase |
Any news? |
Any news? phpmyadmin also need information_schema. |
Hello , this issue has not received a reply for several days. |
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. |
Close because of staled. |
Bug Report
For English only, other languages will not accept.
Before report a bug, make sure you have:
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?
5.0.0-RC1-SNAPSHOT
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
Expected behavior
Get the result from the following SQLs:
Actual behavior
Reason analyze (If you can)
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
Execute these SQLs straightforwardly.
Example codes for reproduce this issue (such as a github link).
The text was updated successfully, but these errors were encountered: