TianWanMing opened a new issue, #34667:
URL: https://github.com/apache/shardingsphere/issues/34667

   ## Bug Report
   
   **For English only**, other languages will not accept.
   
   Before report a bug, make sure you have:
   
   - Searched open and closed [GitHub 
issues](https://github.com/apache/shardingsphere/issues).
   - Read documentation: [ShardingSphere 
Doc](https://shardingsphere.apache.org/document/current/en/overview).
   
   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.5.1
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-JDBC
   ### Expected behavior
   
   ### Actual behavior
   
   ### Reason analyze (If you can)
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   Parsing the sql
   ### Example codes for reproduce this issue (such as a github link).
   
     String sql = "SELECT B.* FROM (SELECT A.* FROM (SELECT * FROM 
ACT_DEPLOY_FORM WHERE FORM_KEY= 1) AS A) AS B";
           CacheOption cacheOption = new CacheOption(128, 1024L);
           SQLParserEngine parserEngine = new SQLParserEngine("Oracle", 
cacheOption);
           ParseASTNode parseASTNode = parserEngine.parse(sql, true);
           SQLStatementVisitorEngine sqlVisitorEngine = new 
SQLStatementVisitorEngine("Oracle");
           SQLStatement sqlStatement = sqlVisitorEngine.visit(parseASTNode);
   


-- 
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.

To unsubscribe, e-mail: 
notifications-unsubscr...@shardingsphere.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to