Results of 1 - 8 of about 8 for mostly (0.002 sec.)
- VACUUM Statement 12652
- The VACUUM statement only has basic support in DuckDB and is mostly provided for PostgreSQL-compatibility. Some variants of it, such as when calling for a given column, recompute the distinct statistics (the number of distinct entities) if
... - https://man.mtool.work/duckdb/2.0/sql/statements/vacuum.html
- Building Extensions 10682
- Extensions can be built from source and installed from the resulting local binary. Building Extensions To build using extension flags, set the BUILD_EXTENSIONS flag to the list of extensions that you want to be built. For example: BUILD_EXT
...ed. Making sure index out of bounds accesses don't trigger a crash. With this flag enabled we remove these checks, this is mostly done to check that the performance hit of these checks is negligible. DESTROY_UNPINNED_BLOCKS When previously pinned block... - https://man.mtool.work/duckdb/2.0/dev/building/building_extensions.html
- Import Data 10013
- Overview The Go client offers two ways to load data into DuckDB in bulk: the high-performance Appender for inserting rows generated in Go, and reading directly from data files such as Parquet, CSV, and JSON. Both are described below. For in
..., columnNames) can also append a subset of columns, leaving other columns at their default values or NULL . It is retained mostly for backward compatibility. Prefer NewTableAppender for this case because its query-based appender is more performant. Rea... - https://man.mtool.work/duckdb/2.0/clients/go/data_import.html
- Tuning Workloads 8693
- DuckDB aims to perform well out of the box, so most workloads do not require any tuning. When tuning is worthwhile, there is no single configuration or magic number that is optimal for every workload: the right settings depend on what you a
...etc.) and caches their output. When it is executed, those steps can be skipped, improving performance. This is beneficial mostly for repeatedly running small queries (with a runtime of < 100ms) with different sets of parameters. Note that it is not a... - https://man.mtool.work/duckdb/2.0/guides/performance/how_to_tune_workloads.html
- Pragmas 8043
- 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
...ic expression, wrap it in TRY instead, e.g., TRY(1 // 0) . Query Verification (for Development) The following PRAGMA s are mostly used for development and internal testing. Deprecated The enable_verification and disable_verification pragmas are depreca... - https://man.mtool.work/duckdb/2.0/configuration/pragmas.html
- Geometry Data Type 7374
- Name Description GEOMETRY Geospatial entity The GEOMETRY data type is used to store and manipulate geometric objects, such as points, lines, and polygons. The GEOMETRY type was part of the spatial extension but became a built-in data type i
...on't contain any vertices. Empty geometries are still valid geometries and can be used in spatial operations, but they are mostly useful for representing the result of topological operations that don't have a valid geometrical representation (e.g., the... - https://man.mtool.work/duckdb/2.0/sql/data_types/geometry.html
- DuckDB_% Metadata Functions 7374
- DuckDB offers a collection of table functions that provide metadata about the current database. These functions reside in the main schema and their names are prefixed with duckdb_ . The resultset returned by a duckdb_ table function may be
...unction provides metadata about the temporary files DuckDB has written to disk, to offload data from memory. This function mostly exists for debugging and testing purposes. Column Description Type path The name of the temporary file. VARCHAR size The s... - https://man.mtool.work/duckdb/2.0/sql/meta/duckdb_table_functions.html
- COPY Statement 7374
- Examples Read a CSV file into the lineitem table, using auto-detected CSV options: COPY lineitem FROM 'lineitem.csv'; Read a CSV file into the lineitem table, using manually specified CSV options: COPY lineitem FROM 'lineitem.csv' (DELIMITE
...ER '|' CSV HEADER; COPY ... TO COPY ... TO exports data from DuckDB to an external CSV, Parquet, JSON or BLOB file. It has mostly the same set of options as COPY ... FROM , however, in the case of COPY ... TO the options specify how the file should be... - https://man.mtool.work/duckdb/2.0/sql/statements/copy.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work