You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2019/12/23 09:04:24 UTC

[GitHub] [incubator-shardingsphere] runjia1987 commented on issue #2263: Must have sharding column with subquery error occurred when use “exists”.

runjia1987 commented on issue #2263: Must have sharding column with subquery  error occurred when use “exists”.
URL: https://github.com/apache/incubator-shardingsphere/issues/2263#issuecomment-568410052
 
 
   Seems you guys do not consider this scenario: "table join itself", which also throws this "must have"  exception. e.g. we optimize limit sql by using "select a.* from table a join(select id from table limit n, m) r using(id).
   I think this is a bug.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services