Closed irwinai closed 2 months ago
Hi @irwinai, can you provide your configuration?
Hi @irwinai, can you provide your configuration?
what configuration??
Hi @irwinai, can you provide your configuration?
updated
The SQL parser is improved in each version, please test the latest version.
Bug Report
Which version of ShardingSphere did you use?
5.1.1
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
Expected behavior
query success
Actual behavior
query with exception
Reason analyze (If you can)
I dont know
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
make query like this select xx.* with join
then you can get the query with exception
The table in the query condition of this question has nothing to do with whether it is divided into tables. This problem exists regardless of whether it is a single table or a divided table. The core of the main problem is that as long as a subquery is joined, and then
x.*
is included in the select condition, an error will be reported.Example codes for reproduce this issue (such as a github link).