While trying to conversions from SQL using large volumes of existing (sample / benchmark) SQL expressions, I have experienced significant issues due to column (or table) names that happen to match reserved keywords. For example:
SELECT COUNTRY FROM COUNTRY_LANGUAGE WHERE LANGUAGE = 'ENGLISH' Calcite appears to require quoting of any name that matches a keyword — in this case LANGUAGE — whereas generally this isn't required since (I guess) the meaning can be inferred from the context. I would be happy to try to contribute an enhancement to address this, but I don't really know the bet place to start in the codebase; even where best to put unit tests to drive the implementation. I am completely new to the Calcite codebase. Can anyone provide me with some pointers on where to look and advice on the most suitable implementation approach?
