[
https://issues.apache.org/jira/browse/CALCITE-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711149#comment-17711149
]
Mihai Budiu commented on CALCITE-5615:
--------------------------------------
I have filed this PR [https://github.com/apache/calcite/pull/3145] with the
contribution to Calcite.
I have tried to file some of the bugs discovered, but some of the tests fail in
one way when invoked from JdbcTest and in another way when invoked from this
program. It must be that the test fixtures produce some slightly different
configurations for the compiler than the "standard" one obtained from
"jdbc:calcite". If someone can help me figure out how to reproduce the same
environment it would be great.
> Run SQLLogicTests using Calcite
> -------------------------------
>
> Key: CALCITE-5615
> URL: https://issues.apache.org/jira/browse/CALCITE-5615
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.34.0
> Reporter: Mihai Budiu
> Priority: Minor
>
> Sqllogictest is a program designed to verify that an SQL database engine
> computes correct results by comparing the results to identical queries from
> other SQL database engines.
> https://www.sqlite.org/sqllogictest/doc/trunk/about.wiki
> The nice thing about SLT is that it contains more than 7 million tests. The
> tests only cover the core of SQL, ideally the portable part across all
> engines. They only test integers, doubles, and strings. So they could
> probably be part of the Calcite slow tests.
> The tests should be structured so that any query execution engine can be used.
> I plan to contribute such an implementation if people think it is useful, but
> I haven't yet worked out all the details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
