linghengqian commented on issue #32189: URL: https://github.com/apache/shardingsphere/issues/32189#issuecomment-2259568326
- @naah69 I believe a Postgresql dialect-specific implementation of the SQL standard's `WITH [RECURSIVE] syntax` has been discussed at https://issues.apache.org/jira/browse/CALCITE-129 and https://github.com/apache/calcite/pull/3480 . - This relates to https://www.postgresql.org/docs/current/queries-with.html#QUERIES-WITH-RECURSIVE and https://github.com/apache/calcite/pull/3480#discussion_r1369643978 . - The problem involved here is that Calcite 1.36.0 breaks the unit test of ShardingSphere, because starting from Calcite 1.36.0 , charset information in SQL began to be parsed correctly. Refer to https://github.com/apache/shardingsphere/pull/29229 and https://github.com/apache/calcite/pull/3429 . - You can submit a PR to fix this issue at any time, or ask the relevant committer how to fix the unit test of ShardingSphere's SQL Federation. I am not the main contributor of the SQL Federation feature. - The general understanding is to update calcite to 1.36.0 and fix the unit test, and then call the relevant calcite internal API in shardingsphere to support parsing `WITH [RECURSIVE] syntax`. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
