Results of 1 - 10 of about 104 for call (0.002 sec.)
- Logging 15106
- 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
...ble_logging . Logs are stored in a special view named duckdb_logs , which can be queried like any standard table. Example: CALL enable_logging(storage = 'memory'); -- Run some queries... SELECT * FROM duckdb_logs; In the CLI client , the default log...uerying. Therefore, the example above passes storage = 'memory' . In other clients, the default log storage is memory , so CALL enable_logging(); suffices. See Log Storages for details. To disable logging, run CALL disable_logging(); To clear the cur...rent log, run CALL truncate_duckdb_logs(); Log Level DuckDB supports different logging levels that control the verbosity of the logs: FATAL :... - https://man.mtool.work/duckdb/2.0/operations_manual/logging/overview.html
- Appender 10315
- Use an appender to insert rows that your Python code produces. It collects rows and writes them together in one SQL statement; this is called flushing. The with block below flushes on successful exit: import duckdb con = duckdb.connect() co
...t. When an exception leaves the block, the buffered rows are discarded and the exception propagates. Outside a with block, call flush() to write the rows and clear() to discard them. There is no close() method. The appender remains usable after flush...() , clear() or leaving a with block. Warning Garbage collection discards buffered rows and emits a ResourceWarning . Call flush() or use a with block to write the rows. Errors and Retrying The appender checks its statement when you create it, w...aint violations raise an exception during flush() . A flush that raises because an earlier result is still open or another call is running on the connection keeps its buffered rows, and so does an interrupted flush. Finish the result or wait for the... - https://man.mtool.work/duckdb/2.0/clients/python/appender.html
- CALL Statement 10161
- The CALL statement invokes the given table function and returns the results. Thanks to the FROM -first syntax and the fact that procedures in DuckDB are implemented as table functions, you can use FROM instead of CALL . Examples Invoke the
...duckdb_functions table function: CALL duckdb_functions(); Invoke the pragma_table_info table function: CALL pragma_table_info('pg_am'); Select only the function... - https://man.mtool.work/duckdb/2.0/sql/statements/call.html
- Write User Defined Functions 9556
- Overview The JDBC driver can register user-defined functions (UDFs) written in Java, including scalar functions and table functions. This page covers building and registering both, from the simple functional-interface overloads to the vecto
...uckdb.DuckDBScalarFunctionBuilder — and register it on a connection with register() . Once registered, the function can be called from SQL by the name passed to withName() . The builder is single-use: it is finalized once register() (or close() ) is...x * w + 10.0) .register(conn); SELECT java_weighted_sum(2.5, 4.0); Variadic Arguments For a variable number of arguments, call withVarArgs() to declare the element type and withVarArgsFunction() to supply the implementation. The callback receives th...g; } return sum; }) .register(conn); } SELECT java_sum_varargs(1, 2, 3, 4); NULL Handling By default, a scalar function is called for every input row, including rows that contain SQL NULL : Callbacks that take Object arguments ( Function , BiFunction... - https://man.mtool.work/duckdb/2.0/clients/java/functions.html
- Security 8860
- This page covers Quack's security posture end to end: what the server exposes, what stays local, the role of a TLS-terminating reverse proxy, and the authentication / authorization callbacks the server runs on every connection and every que
...Reverse Proxy for nginx and Caddy recipes (production and local-test). Authentication and Authorization For every database call, there are two distinct decisions to be made: Authentication : who is the caller? Establishes identity, usually by having...the caller supply a credential (e.g., a token, a password, a client certificate). Authorization : may they do this? Establishes whe...ther an already authenticated caller is allowed to run a particular query, against a particular set of objects. Quack runs these as two separate hooks: the a... - https://man.mtool.work/duckdb/2.0/quack/security.html
- ODBC Extension Functions 8706
- odbc_begin_transaction odbc_bind_params odbc_close odbc_commit odbc_connect odbc_copy odbc_create_params odbc_list_data_sources odbc_list_drivers odbc_query odbc_rollback odbc_begin_transaction odbc_begin_transaction(conn_handle BIGINT) ->
...IT_OFF on the specified connection thus effectively starting an implicit transaction. odbc_commit or odbc_rollback must be called on such connection to complete the transaction. The completion starts another implicit transaction on this connection. S...s NULL ( VARCHAR ). Example: SELECT odbc_close(getvariable('conn')) odbc_commit odbc_commit(conn_handle BIGINT) -> VARCHAR Calls SQLEndTran with SQL_COMMIT argument on the specified connection, completing the current transaction. odbc_begin_transacti...on must be called on this connection before this call for the completion to be effective. See Transaction management for details. Paramete... - https://man.mtool.work/duckdb/2.0/core_extensions/odbc/functions.html
- CREATE MACRO Statement 8242
- The CREATE MACRO statement defines a named, callable SQL expression as a database schema object. Macros may declare parameters, which can be referenced by its expression. Once a macro is created, it may be called by referencing its name and
...before the expression, indicating the macro is a table macro and returns a result set. When omitted, the macro is automatically a scalar macro. The expression can be any valid SQL expression provided the expression's type is aligned with the macro's...precise and detailed overview of the CREATE MACRO statement. Types of Macros The contexts where a particular macro may be called depends on the data type of its result value: * Scalar macros evaluate to a scalar value. For scalar macros, the express...ion can either be a simple expression, or a scalar subquery. * Table macros return a tabular result: when called, they act essentially as table functions and return a table value. Their expression can be a SELECT statement, or a call... - https://man.mtool.work/duckdb/2.0/sql/statements/create_macro.html
- Iceberg Functions 7856
- The iceberg extension provides the following functions: Function Description iceberg_scan(source) Reads an Iceberg table from a path. iceberg_metadata(source) Returns the manifest entries of an Iceberg table. iceberg_snapshots(source) Retur
...not change reserved Iceberg table properties. In particular, format-version can only be changed with ALTER TABLE ... SET . CALL set_iceberg_table_properties('iceberg_catalog.default.my_table', { 'write.update.mode': 'merge-on-read' }); CALL remove_ic...erg catalogs allow arbitrary key-value properties to be attached at the schema (namespace) level. These properties are typically used to record ownership, descriptions, default storage locations, or any other metadata that applies to every table in a...ve_iceberg_schema_properties(schema, property_list) Removes properties from the specified schema. -- Set schema properties CALL set_iceberg_schema_properties(iceberg_catalog.default, { 'owner': 'analytics-team', 'description': 'Default analytics sche... - https://man.mtool.work/duckdb/2.0/core_extensions/iceberg/iceberg_functions.html
- AutoComplete Extension 7624
- The autocomplete extension adds support for autocomplete in the CLI client . The extension is shipped by default with the CLI client. Behavior For the behavior of the autocomplete extension, see the documentation of the CLI client . Functio
...y_string . Example SELECT * FROM sql_auto_complete('SEL'); Returns: suggestion suggestion_start SELECT 0 DELETE 0 INSERT 0 CALL 0 LOAD 0 CALL 0 ALTER 0 BEGIN 0 EXPORT 0 CREATE 0 PREPARE 0 EXECUTE 0 EXPLAIN 0 ROLLBACK 0 DESCRIBE 0 SUMMARIZE 0 CHECKPOI... - https://man.mtool.work/duckdb/2.0/core_extensions/autocomplete.html
- Import Data 7469
- Overview The Rust client offers two ways to get data into DuckDB in bulk: the high-performance Appender for inserting rows from Rust, and reading directly from data files such as Parquet, CSV, and JSON. Both are described below. Appender Th
...])?; app.append_row(params![3, 4])?; app.flush()?; Ok(()) } To append many rows from an iterator of parameter lists in one call, use append_rows() : app.append_rows([[1, 2], [3, 4], [5, 6], [7, 8], [9, 10]])?; Additional constructors target tables ou...keys only when the buffer is flushed, so append_row() may return Ok for a row that later fails a constraint check. Always call flush() explicitly and check its result before the appender is dropped. Dropping an appender flushes any remaining rows, b...[], |row| row.get::<_, i64>(0))?; assert_eq!(count, row_count); Ok(()) } A Transaction rolls back by default when dropped. Call set_drop_behavior(DropBehavior::Commit) to commit on drop instead, or call tx.commit() explicitly. The other DropBehavior... - https://man.mtool.work/duckdb/2.0/clients/rust/data_import.html
DuckDB 2.0 Documentation / man.mtool.work