Hi Larry,

It seems that you are interested mainly in the SqlParser component of
Calcite.
You can check if it satisfies your needs by adding some tests in
SqlParserTest [1] and/or BabelParserTest [2] using the DB2 dialect.
If you encounter problems with things that are not supported log JIRA
tickets or ask for help in the dev list.

Best,
Stamatis

[1]
https://github.com/apache/calcite/blob/bc4cfa32833649f44f6f2e9455229fa0355ad81e/testkit/src/main/java/org/apache/calcite/sql/parser/SqlParserTest.java

[2]
https://github.com/apache/calcite/blob/bc4cfa32833649f44f6f2e9455229fa0355ad81e/babel/src/test/java/org/apache/calcite/test/BabelParserTest.java


On Thu, Dec 22, 2022 at 7:28 PM Larry LeFever <[email protected]>
wrote:

> I'm developing a codegen tool to facilitate development of custom reports
> where I work.
>
> One step in the codegen process reads the top-level column-aliases of a
> usually very complex report-backing query (lots of subqueries, some use of
> listagg, etc.) and uses those aliases to generate a db-row POJO.
>
> I've used ANTLR's SQLLite generated parser for that, but it encounters DB2
> for AS/400 specific SQL it can't handle.
>
> I believe I've seen in some of the documentation a component of Calcite for
> the DB2 SQL-dialect.
>
> So, I'm wondering if I could incorporate Calcite into my codegen tool to
> use its SQL-parsing functionality in the db-row POJO generating part of my
> codegen tool.
>
> Any advice would be much appreciated.
>
> Larry LeFever
>

Reply via email to