Open CatInRl opened 2 years ago
@CatInRl I have the same problem. Have you solved it
no. we use select 1 ... limit 1
instead. @zhoubin7
@CatInRl Hello, I'm a new comer for shardingsphere, can you assign this issue to me? thanks!
@CatInRl Hello, I'm a new comer for shardingsphere, can you assign this issue to me? thanks!
@TeslaCN Can you assign this issue to him?
@CatInRl Welcome, I will assign this issue to you.
@strongduanmu sorry to bother you, I think he wants to assign the issue to me
@CatInRl @wuxihao01 Sorry for the mistake. Assigned.
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.2.0
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
Expected behavior
return true or false
Actual behavior
throw exception below:
Reason analyze (If you can)
ShardingSphere-JDBC just does a union on the
exists
result of the sharding tables and returns two rowSteps 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).
https://github.com/CatInRl/sharding-jdbc-demo
curl 127.0.0.1:8080/order/exists?orderName=order1