Results of 1 - 10 of about 34 for calls (0.002 sec.)
- HTTP User-Agent 14907
- HTTP User-Agent Core DuckDB sets the default user-agent as follows: duckdb/v2.0.0(osx_arm64) cli which indicates the DuckDB version, the platform and the client API (the value of the duckdb_api setting, e.g., cli , capi or cpp ). If the cus
...include the following. Extensions Azure Azure uses the Azure SDK which sets its own user agents. For identity and storage calls you may see respectively strings like these: via Azure Identity: azsdk-cpp-identity/1.11.0 (Darwin 25.2.0 arm64 Darwin Ker...:05 PST 2025; root:xnu-12377.61.12~1/RELEASE_ARM64_T6020 Cpp/201402) Delta (and Unity Catalog) The Delta extension employs calls from DuckDB core, tagged as the DuckDB default above, and also has calls originating from the Delta Kernel, which may look...like: object_store/0.12.5 Unity Catalog calls also use a mix of DuckDB default user-agents, and the Delta style agent above. HTTPFS - HTTPS/S3 Calls via HTTPFS the exte... - https://man.mtool.work/duckdb/2.0/operations_manual/user_agents.html
- Write User Defined Functions 11855
- 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
...cache or constant-fold its result for repeated inputs. Call withVolatile() for a function whose output can change between calls with the same arguments — for example one that reads external state — so the engine evaluates it for every row. Error Hand...tput vectors and returns the number of rows written, with access to the bind, global-init, and local-init data. The engine calls it repeatedly until it returns 0 . import java.sql.Connection; import java.sql.DriverManager; import java.util.concurrent....Rows in Chunks The example above writes every row in a single apply call, but a table function is not expected to. DuckDB calls apply repeatedly, each time passing a fresh output chunk that holds up to output.capacity() rows (2,048 by default). Fill... - https://man.mtool.work/duckdb/2.0/clients/java/functions.html
- Write User Defined Functions 11088
- Overview The Rust client can register user-defined functions written in Rust: scalar functions with the vscalar feature and table functions with the vtab feature. Both operate on DuckDB's columnar data chunks, so a single call processes a b
...function is a type that implements the VScalar trait, registered on a connection with register_scalar_function() . DuckDB calls the function's invoke() once per data chunk, passing a batch of input rows and expecting the corresponding output values w...d to register_scalar_function() : SELECT add_one(41); The associated type State holds any per-function state shared across calls; use () when none is needed. The example reads its input as a typed slice for brevity and assumes non-null input; a produc...ces one chunk of rows per call. It fills the output vectors and sets the chunk length. A length of 0 ends the scan. DuckDB calls it repeatedly until the scan is done, so a large result is delivered over several calls. parameters declares the function'... - https://man.mtool.work/duckdb/2.0/clients/rust/functions.html
- ODBC API Overview 8484
- Installation To use the DuckDB ODBC client, visit the ODBC installation page . The latest stable version of the DuckDB ODBC client is 2.0.0. This page describes the DuckDB ODBC driver, which lets other applications connect to DuckDB . To co
...river is a DBMS implementation of the ODBC API, which handles all the internals of that DBMS. The DM maps user application calls of ODBC functions to the correct ODBC driver that performs the specified function and returns the proper values. DuckDB OD... - https://man.mtool.work/duckdb/2.0/clients/odbc/overview.html
- Migrating Python Code to DuckDB 2.0 8484
- This page lists what Python code written for DuckDB 1.x must change to run on DuckDB 2.0. Each item gives the 1.x form, the 2.0 form and the page that explains it. For changes outside the Python client, see Migrating to DuckDB v2.0 . Python
...many(n) , rel.execute() and rel.fetch_df_chunk() . 2.0: these methods are gone, because a relation keeps no result between calls and runs its query again on every read. To keep a fetchone() or fetchmany() loop for a SQL query, create its result with c...con.abort() , and the next execute() replaces the open result. See Open Results . One connection in several threads. 1.x: calls from several threads on one connection waited for each other. 2.0: a call while another thread uses the connection raises... - https://man.mtool.work/duckdb/2.0/clients/python/migration.html
- Appender 8324
- 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
...fails, append_row , append_rows and flush() raise an exception until you call clear() . Connections and Threads Concurrent calls on the same appender raise an exception rather than wait. Calls from a callback during a flush also raise an exception. Us... - https://man.mtool.work/duckdb/2.0/clients/python/appender.html
- Pragmas 8324
- 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
...ning. Use SET name = value instead. The warning becomes an error when warnings_as_errors is enabled. Function-style PRAGMA calls (for example, PRAGMA table_info('table_name') ) and the SQLite-compatible PRAGMA table_info = 'table_name' form are unaffe...filing = 'query_tree_optimizer'; Database drivers and other applications can also access profiling information through API calls, in which case users can disable any other output. Even though the parameter reads no_output , it is essential to note tha...t this only affects printing to the configurable output. When accessing profiling information through API calls, it is still crucial to enable profiling: SET enable_profiling = 'no_output'; Profiling Output By default, DuckDB prints p... - https://man.mtool.work/duckdb/2.0/configuration/pragmas.html
- INSERT Statements 8324
- INSERT statements are the standard way of loading data into a relational database. When using INSERT statements, the values are supplied row-by-row. While simple, there is significant overhead involved in parsing and processing individual I
...ignificantly slow down your program. Tip If you absolutely must use INSERT statements in a loop to load data, wrap them in calls to BEGIN TRANSACTION and COMMIT . Syntax An example of using INSERT INTO to load data in a table is as follows: CREATE TAB... - https://man.mtool.work/duckdb/2.0/data/insert.html
- TRY Expression 8324
- The TRY expression ensures that errors caused by the input rows in the child (scalar) expression result in NULL for those rows, instead of causing the query to throw an error. The TRY expression was inspired by the TRY_CAST expression . Exa
...mples The following calls return errors when invoked without the TRY expression. When they are wrapped into a TRY expression, they return NULL : Cas... - https://man.mtool.work/duckdb/2.0/sql/expressions/try.html
- UPDATE EXTENSIONS 8020
- The UPDATE EXTENSIONS statement allows synchronizing the locally installed extension state with the repository that published a given extension. This statement is the recommended way to keep up to date with new features or bug fixes being r
...ension is different (using the ETag as proxy) than the local available one. This ensures that subsequent UPDATE EXTENSIONS calls – if the remote state has not changed – are inexpensive. If a change is found for a given extension, DuckDB performs the f... - https://man.mtool.work/duckdb/2.0/sql/statements/update_extensions.html
DuckDB 2.0 Documentation / man.mtool.work