Hi community,
A quick survey about the API of SQL parser engine was given yesterday. Thanks for much feedback from the community, which gave us a better idea to support this feature. At last, we plan to adopt that most-expected way to improve the function and re-prepare the incoming 5.0.0-alpha release. I will finish this task ASAP. Please wait for my good news. BTW, if you want to learn more, please look at [1] [1] https://github.com/apache/shardingsphere/issues/7869 Juan Pan (Trista) Senior DBA & PMC of Apache ShardingSphere E-mail: [email protected] On 10/21/2020 19:37，Juan Pan<[email protected]> wrote： Hi community, I am glad to announce that ShardingSphere will provide an independent SQL parser engine for parsing SQLs! I believe you will have some of the scenarios or use the SQL parser engine to get a parsed AST. From now on, you will have another option for your cases. Here are some of the advantages for ShardingSphere parser engine. Advantages Mostly perfect SQL statements supported for MySQL database Mostly perfect SQL statements supported for PostgreSQL database Basically SQL statements supported for SQLServer database Basically SQL statements supported for Oracle database SQL parsed result cache for the parsing performance AST parsed result and SQLStatement parsed result are provided meanwhile Simple extension approach for SQLStatement visitors Simple supplement approach and for SQL definition Continuous improvement for the much better feature in the future. 5.x release will include this one, please wait for our good news! 😉 Juan Pan (Trista) Senior DBA & PMC of Apache ShardingSphere E-mail: [email protected]
