Results of 1 - 3 of about 3 for exhaustive (0.001 sec.)
- Overview 11924
- How is DuckDB Tested? Testing is vital to make sure that DuckDB works properly and keeps working properly. For that reason, we put a large emphasis on thorough and frequent testing: * We run a batch of small tests on every commit using GitH
...ub Actions , and run a more exhaustive batch of tests on pull requests and commits in the main branch. * We use a fuzzer , which automatically reports issues fou... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/overview.html
- Run Queries 8147
- Overview A Connection runs SQL through two families of methods: The execute_* methods ( execute() and execute_batch() ) send statements that do not return rows, such as INSERT or DDL, and report the number of affected rows. The query_* meth
...ow.get(0)?; let strukt: Value = row.get(1)?; println!("{list:?} {strukt:?}"); } Value , ValueRef , and Type are marked non-exhaustive, so a match over them should include a wildcard arm to stay forward-compatible as DuckDB adds types. To read whole result... - https://man.mtool.work/duckdb/2.0/clients/rust/querying.html
- Logging 7813
- DuckDB implements a logging mechanism that provides users with detailed information about events such as query execution, performance metrics and system events. Warning Logs may contain sensitive information, including secrets and credentia
...f each structure log type simply run: DESCRIBE FROM duckdb_logs_parsed('HTTP'); List of Available Log Types This is a (non-exhaustive) list of the available log types in DuckDB. Log Type Description Structured QueryLog Logs which queries are executed in Du... - https://man.mtool.work/duckdb/2.0/operations_manual/logging/overview.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work