sushu0 commented on issue #40262: URL: https://github.com/apache/shardingsphere/issues/40262#issuecomment-6271870860
Hi @makssent, I would like to pick this up and aim to have a tested draft patch by October 23, 2026 (UTC). I have checked current master (`e3ab362512ee`) and traced the failure to Firebird `identifier -> unreservedWord`: `KEY`, `TEXT`, and `COMMENT` are tokenized but not accepted there. The related #40178 and #40179 do not cover these words. I plan to reproduce the failure in Parser IT, make the smallest Firebird-only grammar correction, add explicit `AS` and implicit column-alias regressions for all three words, and run the existing Firebird parser cases to protect their other uses. I will check the Firebird 5.0 reference together with the versioned engine grammar/lexer, especially the context-sensitive treatment of `COMMENT`; I have not yet run a live Proxy/server comparison and will keep that distinction explicit. @strongduanmu, would you be available to mentor/review this scoped parser fix, or point me to an appropriate parser mentor? Please let me know if someone is already working on it or if this scope should be adjusted. Codex is assisting with investigation, implementation, and tests. Any draft PR will disclose the affected files and keep the human-review requirement explicit. -- 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]
