Results of 1 - 6 of about 6 for coverage (0.003 sec.)
- Python 13051
- The DuckDB Python package has its own repository at duckdb/duckdb-python and uses nanobind 3 to create Python bindings with DuckDB. Prerequisites This guide assumes: You have a full clone of the DuckDB Python package source, including its g
...fast tests only (excludes slow directory): uv run --no-build-isolation pytest ./tests --verbose --ignore=./tests/slow Test Coverage Build with coverage (compiles the extension with --coverage into build/coverage/ for C++ coverage), then run the tests und...er coverage: COVERAGE=1 uv sync --no-build-isolation -v --reinstall -p 3.13 COVERAGE=1 uv run --no-build-isolation coverage run -m pyt...est ./tests --verbose Check Python coverage: uv run coverage html -d htmlcov-python uv run coverage report --format=markdown Check C++ coverage: uv run gcovr \ --gcov... - https://man.mtool.work/duckdb/2.0/dev/building/python.html
- Spatial Functions 8975
- Function Index Scalar Functions Function Summary DuckDB_PROJ_Compiled_Version Returns a text description of the PROJ library version that this instance of DuckDB was compiled against. DuckDB_Proj_Version Returns a text description of the PR
...e first geometry \"properly\" contains the second geometry ST_ConvexHull Returns the convex hull enclosing the geometry ST_CoverageInvalidEdges Returns the invalid edges in a polygonal coverage, which are edges that are not shared by two polygons. ST_Cov...erageSimplify Simplify the edges in a polygonal coverage, preserving the coverage by ensuring that there are no seams between the resulting simplified polygons. ST_CoverageUnion U...nion all geometries in a polygonal coverage into a single geometry. ST_CoveredBy Returns true if geom1 is "covered by" geom2 ST_Covers Returns true if the geom1 "cove... - https://man.mtool.work/duckdb/2.0/core_extensions/spatial/functions.html
- Profiling 8719
- Profiling is essential to help understand why certain queries exhibit specific performance characteristics. DuckDB contains several built-in features to enable query profiling, which this page covers. For a high-level example of using EXPLA
...ble_profiling , enable_profile Turn on profiling query_tree query_tree , json , query_tree_optimizer , no_output profiling_coverage Set the operators to profile SELECT SELECT , ALL profiling_output Set a profiling output file Console A filepath profiling...es profiling with the specified options. CALL enable_profiling( format := 'json', save_location := '/path/to/output.json', coverage := 'select', metrics := ['query.sql', 'query.total_time', 'operator.timing'] ); Parameter Type Description metrics LIST ,...d, has no effect (detailed profiling information is always collected) save_location VARCHAR File path for profiling output coverage VARCHAR Query coverage: 'select' or 'all' format VARCHAR Output format: 'query_tree' , 'json' , 'query_tree_optimizer' , '... - https://man.mtool.work/duckdb/2.0/dev/profiling.html
- ODBC Extension 8646
- Please note that DuckDB also offers an ODBC client , which allows you to connect to DuckDB via ODBC from other applications. The odbc_scanner extension allows connecting to other databases (using their ODBC drivers ) and run queries with th
...ommit_id⟩/v1.2.0/⟨platform⟩/odbc_scanner.duckdb_extension.gz'; Support Status of DBMS-Specific Types Tier 1: Oracle: types coverage status SQL Server: types coverage status DB2: types coverage status Tier 2: PostgreSQL: basic types covered MySQL/MariaDB:...basic types covered Firebird: types coverage status Tier 3: Snowflake: types coverage status ClickHouse: basic types covered Spark: basic types covered Arrow Flight SQ... - https://man.mtool.work/duckdb/2.0/core_extensions/odbc/overview.html
- Pragmas 7933
- The PRAGMA statement is a SQL extension adopted by DuckDB from SQLite. PRAGMA statements can be issued in a similar manner to regular SQL statements. PRAGMA commands may alter the internal state of the database engine, and can influence the
...f the format, enable_profiling is mandatory to enable profiling. PRAGMA enable_profiling; PRAGMA enable_profile; Profiling Coverage By default, the profiling coverage is set to SELECT . SELECT runs the profiler for each operator in the physical plan of a...SELECT statement. SET profiling_coverage = 'SELECT'; By default, the profiler does not emit profiling information for other statement types ( INSERT INTO , ATTACH..., etc.). To run the profiler for all statement types, change this setting to ALL . SET profiling_coverage = 'ALL'; Profiling Format The format of enable_profiling can be specified as query_tree , json , query_tree_optimizer , or... - https://man.mtool.work/duckdb/2.0/configuration/pragmas.html
- Configuration 7457
- DuckDB has a number of configuration options that can be used to change the behavior of the system. The configuration options can be set using either the SET statement or the PRAGMA statement . They can be reset to their original values usi
..._output The file to which profiler output is written. When empty, the output is printed to the terminal. VARCHAR profiling_coverage The profiling coverage, either SELECT (only SELECT queries) or ALL (all queries are profiled). VARCHAR SELECT profiling_re...d via enable_arrow_string_view. BOOLEAN false GLOBAL profiling_mode Deprecated setting. Use enable_profiling and profiling_coverage instead. VARCHAR NULL LOCAL s3_access_key_id S3 Access Key ID VARCHAR NULL GLOBAL s3_endpoint S3 Endpoint VARCHAR NULL GLO... - https://man.mtool.work/duckdb/2.0/configuration/overview.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work