Results of 1 - 5 of about 5 for sqllogictests (0.001 sec.)
- sqllogictest Introduction 12483
- For testing plain SQL, we use an extended version of the SQL logic test suite, adopted from SQLite . Every test is a single self-contained file located in the test/sql directory. To run tests located outside of the default test directory, s
...d in the test directory are automatically added to the test suite. Note that the extension of the test is significant. The sqllogictests should either use the .test extension, or the .test_slow extension. The .test_slow extension indicates that the test takes...ion for all unit tests, except those involving larger datasets (more than ~10-100 rows). Editors & Syntax Highlighting The sqllogictests are not exactly an industry standard, but several other systems have adopted them as well. Parsing sqllogictests is intent...ult. A syntax highlighter exists for Visual Studio Code . We have also made a fork that supports the DuckDB dialect of the sqllogictests . You can use the fork by installing the original, then copying the syntaxes/sqllogictest.tmLanguage.json into the install... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/intro.html
- Debugging 9835
- The purpose of the tests is to figure out when things break. Inevitably changes made to the system will cause one of the tests to fail, and when that happens the test needs to be debugged. First, it is always recommended to run in debug mod
...ing which tests to run section. After that, a debugger can be attached to the program and the test can be debugged. In the sqllogictests it is normally difficult to break on a specific query, however, we have expanded the test suite so that a function called..., by default all the fast tests are run. A specific test can be run by adding the name of the test as an argument. For the sqllogictests, this is the relative path to the test file. To run only a single test: build/debug/test/unittest test/sql/projection/test... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/debugging.html
- Multiple Connections 8309
- For tests whose purpose is to verify that the transactional management or versioning of data works correctly, it is generally necessary to use multiple connections. For example, if we want to verify that the creation of tables is correctly
...e a query in con2 that checks that the table is not accessible yet until committed. We can use multiple connections in the sqllogictests using connection labels . The connection label can be optionally appended to any statement or query . All queries with the... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/multiple_connections.html
- Loops 7868
- Loops can be used in sqllogictests when it is required to execute the same query many times but with slight modifications in constant values. For example, suppose we want to fire off 100 queries that check for the presence of the values 0..
... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/loops.html
- Result Verification 7427
- The standard way of verifying results of queries is using the query statement, followed by the letter I times the number of columns that are expected in the result. After the query, four dashes ( ---- ) are expected followed by the result v
...LECT 42, 84 UNION ALL SELECT 10, 20; ---- 42 84 10 20 Hashes and Outputting Values Besides direct result verification, the sqllogic test suite also has the option of using MD5 hashes for value comparisons. A test using hashes for result verification looks lik...prefer not to use this field and rely on ORDER BY in the query to generate deterministic query answers. However, existing sqllogictests use this field extensively, hence it is important to know of its existence. Query Labels Another feature that can be used... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/result_verification.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work