Results of 1 - 10 of about 69 for level (0.002 sec.)
- Logging 12839
- 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
...or details. To disable logging, run CALL disable_logging(); To clear the current log, run CALL truncate_duckdb_logs(); Log Level DuckDB supports different logging levels that control the verbosity of the logs: FATAL : Only logs fatal errors ERROR : Lo...gs and errors (default) DEBUG : Logs detailed debugging information TRACE : Logs very detailed tracing information The log level can be set using: CALL enable_logging(level = 'debug'); Warnings DuckDB emits warnings, for example when you use deprecate...d syntax or a deprecated setting, through the logging system at the WARNING level. In the CLI, warnings are printed by default. To capture them from any client, or to inspect them after the fact, enable l... - https://man.mtool.work/duckdb/2.0/operations_manual/logging/overview.html
- ODBC API on Linux 12386
- Driver Manager A driver manager is required to manage communication between applications and the ODBC driver. We tested and support unixODBC that is a complete ODBC driver manager for Linux. Users can install it from the command line: On De
...sed on the user home directory to setup the ODBC init files. batch ./unixodbc_setup.sh -u The -s option changes the system level files that will be visible for all users, because of that it requires root privileges. batch sudo ./unixodbc_setup.sh -s T...sage: ./unixodbc_setup.sh [options] Example: ./unixodbc_setup.sh -u -db ~/database_path -D ~/driver_path/libduckdb_odbc.so Level: -s: System-level, using 'sudo' to configure DuckDB ODBC at the system-level, changing the files: /etc/odbc[inst].ini -u:...User-level, configuring the DuckDB ODBC at the user-level, changing the files: ~/.odbc[inst].ini. Options: -db database_path>: the Du... - https://man.mtool.work/duckdb/2.0/clients/odbc/linux.html
- Enum Data Type 10195
- Name Description ENUM Dictionary representing all possible string values of a column The enum type represents a dictionary data structure with all possible unique values of a column. For example, a column storing the days of the week can be
...vious section), and the comparison will be done lexicographically as with strings: CREATE TABLE tasks (name TEXT, priority_level priority); INSERT INTO tasks VALUES ('a', 'low'), ('b', 'medium'), ('c', 'high'); -- WARNING! -- Equivalent to `WHERE prio...rity_level::VARCHAR >= 'medium'` SELECT * FROM tasks WHERE priority_level >= 'medium'; -- Misses the 'high' priority task! name prior...ity_level b medium So, if you want to e.g. "get all priorities at or above medium " then explicitly cast to the enum type: SELECT *... - https://man.mtool.work/duckdb/2.0/sql/data_types/enum.html
- Configuration 9968
- 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
...GB. SET memory_limit = '10GB'; Configure the system to use 1 thread. SET threads TO 1; Turn logging on and set the logging level to debug . For additional details on logging levels, see Log Level . In the CLI client, the default log storage ( shell_lo...ried, so we switch to the memory log storage first: SET logging_storage = 'memory'; SET enable_logging = true; SET logging_level = 'debug'; Write a single log message with the debug level and a connection scope: SELECT write_log('A new client has conn...ected.', level := 'debug', scope := 'connection'); Write a single log message with a debug level and a connection scope and a custom log_... - https://man.mtool.work/duckdb/2.0/configuration/overview.html
- CREATE TRIGGER Statement 9855
- New The CREATE TRIGGER feature was introduced in DuckDB 2.0. The CREATE TRIGGER statement registers a trigger: a set of SQL statements that run automatically in response to INSERT , UPDATE , or DELETE events on a table. Examples Record ever
...y statement that modifies a table in an audit table using a statement-level AFTER trigger. The REFERENCING OLD TABLE and NEW TABLE clauses expose the rows before and after the change as transition t...0 WHERE id <= 2; SELECT * FROM audit; id old_val new_val 1 10 100 2 20 200 Fire a trigger once per affected row with a row-level AFTER trigger. Row-level triggers refer to the affected row through the NEW and OLD qualifiers: CREATE TABLE t (id INTEGER...the statement. The triggered statement can refer to the affected row through NEW (for INSERT ) and OLD (for DELETE ). Row-level UPDATE triggers are not yet supported; see the limitations . FOR EACH STATEMENT fires the trigger once per statement, rega... - https://man.mtool.work/duckdb/2.0/sql/statements/create_trigger.html
- Profile and Monitor 9615
- Overview The Go client can observe query execution: it can retrieve per-operator profiling metrics after a query runs, and register a log storage that receives DuckDB's log messages. Both are described below. Profiling Profiling information
...kdb.RegisterLogStorage() , giving it a name and a duckdb.LoggerCallbacks whose DefaultLoggerCallback receives each entry's level, type, and message: connector, err := duckdb.NewConnector("", nil) check(err) defer connector.Close() err = duckdb.Registe...rLogStorage(connector, "my_log_storage", duckdb.LoggerCallbacks{ DefaultLoggerCallback: func(level, logType, logMsg string) { log.Printf("[%s] %s: %s", level, logType, logMsg) }, }) check(err) // Enable logging, then poin...t it at the registered storage. db := sql.OpenDB(connector) _, err = db.Exec(`CALL enable_logging(level = 'info')`) check(err) _, err = db.Exec(`SET logging_storage = 'my_log_storage'`) check(err) Logging is off by default, so... - https://man.mtool.work/duckdb/2.0/clients/go/profiling.html
- GROUPING SETS 8922
- GROUPING SETS , ROLLUP and CUBE can be used in the GROUP BY clause to perform a grouping over multiple dimensions within the same query. Note that this syntax is not compatible with GROUP BY ALL . Examples Compute the average income along t
...oduces the grouping sets (country, city, zip), (country, city), (country), () . This can be useful for producing different levels of detail of a group by clause. This produces n+1 grouping sets where n is the amount of terms in the ROLLUP clause. CUBE...3 3 NULL 1 2023 4 10 0 2023 4 11 0 2023 4 12 0 2023 4 NULL 1 2023 NULL NULL 3 NULL NULL NULL 7 In this example, the lowest level of grouping is at the month level, defined by the grouping set (y, q, m) . Result rows corresponding to that level are sim...GROUPING_ID(y, q, m) function returns 0 for those. The grouping set (y, q) results in super-aggregate rows over the month level, leaving a NULL -value for the m column, and for which GROUPING_ID(y, q, m) returns 1 . The grouping set (y) results in su... - https://man.mtool.work/duckdb/2.0/sql/query_syntax/grouping_sets.html
- Spatial Functions 8809
- 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
...g all of the source input's points, and which can be used to create polygons from points. The ratio parameter dictates the level of concavity; 1.0 returns the convex hull; and 0 indicates to return the most concave hull possible. Set allowHoles to a n...s a polygonized representation of the input geometries ST_QuadKey Compute the quadkey for a given lon/lat point at a given level. ST_ReducePrecision Returns the geometry with all vertices reduced to the given precision ST_RemoveRepeatedPoints Remove r...RING. ST_TileEnvelope The ST_TileEnvelope scalar function generates tile envelope rectangular polygons from specified zoom level and tile indices. ST_Touches Returns true if the geometries touch ST_Transform Transforms a geometry between two coordinat... - https://man.mtool.work/duckdb/2.0/core_extensions/spatial/functions.html
- Avro Extension 8470
- The avro extension enables DuckDB to read Apache Avro files. The avro extension was released as a community extension in late 2024 and became a core extension in early 2025. The read_avro Function The extension adds a single DuckDB function
...on type ["int"] also becomes a DuckDB INTEGER . The extension also "flattens" the Avro schema. Avro defines tables as root-level "record" fields, which are the same as DuckDB STRUCT fields. For more convenient handling, this extension turns the entrie...s of a single top-level record into top-level columns. Implementation Internally, this extension uses the "official" Apache Avro C API , albeit wi... - https://man.mtool.work/duckdb/2.0/core_extensions/avro.html
- R-Tree Indexes 8470
- The spatial extension provides support for spatial indexing through the R-tree extension index type. Why Should I Use an R-Tree Index? When working with geospatial datasets, it is very common that you want to filter rows based on their spat
...s the name of the R-tree index as an argument and returns a table with the following columns: Column name Type Description level INTEGER The level of the node in the R-tree. The root node has level 0 bounds BOX_2DF The bounding box of the node row_id...ee index. Notice how the area of the bounding boxes of the branch nodes -- decreases as we go deeper into the tree. SELECT level, bounds::GEOMETRY AS geom, CASE WHEN row_id IS NULL THEN st_area(geom) ELSE NULL END AS area, row_id, CASE WHEN row_id IS...ndex_dump('my_idx') ORDER BY area DESC; ┌───────┬──────────────────────────────┬────────────────────┬────────┬─────────┐ │ level │ geom │ area │ row_id │ kind │ │ int32 │ geometry │ double │ int64 │ varchar │ ├───────┼──────────────────────────────┼──... - https://man.mtool.work/duckdb/2.0/core_extensions/spatial/r-tree_indexes.html
DuckDB 2.0 Documentation / man.mtool.work