Wrong LIMIT rewrite while using nested SELECT

[joooohnli]

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 more than 7 days 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?

3.1.0

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

Sharding-JDBC

Expected behavior

Actual behavior

Reason analyze (If you can)

io.shardingsphere.core.parsing.parser.context.limit.Limit#rewrite

io.shardingsphere.core.routing.router.sharding.ParsingSQLRouter#processLimit

I guess it is related to the wrong sql parsing.

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

Run it with PreparedStatement:

SELECT MIN(momentID) FROM (SELECT momentID FROM LatestMoment WHERE momentID < ? ORDER BY momentID DESC LIMIT ?)

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

[terrymanu]

Do not support subquery if not on single sharding data node.
Please note, we want focus SQL more make sense for sharding databases, not for all SQL