We already have the switches you’d need: you can control the dialect accepted by Calcite’s parser by setting the “conformance” property [1], and the JDBC adapter generates SQL appropriate for the target database by inferring the target database's “dialect” [2].
What’s missing is a lot of testing of the various combinations of source and target dialects. Julian [1] https://calcite.apache.org/apidocs/org/apache/calcite/sql/validate/SqlConformance.html <https://calcite.apache.org/apidocs/org/apache/calcite/sql/validate/SqlConformance.html> [2] https://calcite.apache.org/apidocs/org/apache/calcite/sql/SqlDialect.html <https://calcite.apache.org/apidocs/org/apache/calcite/sql/SqlDialect.html> > On Mar 13, 2017, at 8:11 PM, [email protected] wrote: > > I am thinking Calcite should be helpful for a SQL migration (making SQL wrote > for database A work with database B, includes SQL syntax and potential query > optimization), I am new to Calcite and this mailing list, I’d appreciate if > anyone here can help point me to a direction where to start. > > Thanks > Herman > >
