Results of 1 - 10 of about 17 for positional (0.002 sec.)
- Prepared Statements 12294
- DuckDB supports prepared statements where parameters are substituted when the query is executed. This can improve readability and is useful for preventing SQL injections . Syntax There are three syntaxes for denoting parameters in prepared
...statements: auto-incremented ( ? ), positional ( $1 ), and named ( $param ). Note that not all clients support all of these syntaxes, e.g., the JDBC client only supports...rts_with(name, ?) AND age >= ?; Using the CLI client, the statement is executed as follows. EXECUTE query_person('B', 40); Positional Parameters: $1 Prepared statements can use positional parameters, where parameters are denoted with an integer ( $1 , $2 )...E multiplier = 100; EXECUTE compute; result 4200 The fallback applies to named parameters only. Auto-incremented ( ? ) and positional ( $1 ) parameters are matched by position and are never filled from a session variable, even one whose name is a number su... - https://man.mtool.work/duckdb/2.0/sql/query_syntax/prepared_statements.html
- CREATE MACRO Statement 11673
- 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
...ed list of expressions appearing between the parentheses following the macro's name. Parameter values may be passed either positionally or by name. Positional parameter passing means that only the value expression is passed; In contrast to positional param...work! Instead, the = is interpreted as comparison operator. This effectively turns the - intended - named parameter into a positional parameter passing the result of comparing the parameter name with the parameter value expression. If a macro call contains...named parameters, then they must appear after any positional parameters. In other words, any positional parameters must appear "in the front"; while all named parameters must appear "... - https://man.mtool.work/duckdb/2.0/sql/statements/create_macro.html
- PREPARE, EXECUTE, and DEALLOCATE Statements 11518
- The PREPARE statement creates a prepared statement for later execution. The EXECUTE statement runs it with optional arguments. The DEALLOCATE statement removes it. For details about auto-incremented, positional, and named parameters, see Pr
...tement with named arguments: EXECUTE query_person(name_start := 'B', minimum_age := 40); Execute a prepared statement with positional arguments: EXECUTE add_values(20, 22); Syntax DEALLOCATE Remove a prepared statement: DEALLOCATE query_person; The optiona... - https://man.mtool.work/duckdb/2.0/sql/statements/prepare.html
- Writing to Iceberg 10724
- The DuckDB iceberg extension supports writing to Iceberg tables when an Iceberg catalog is attached. Writing to a table read directly from storage with iceberg_scan is not supported: the catalog is required to commit the new table metadata.
...TE FROM iceberg_catalog.sales.events WHERE event_time < TIMESTAMP '2026-01-01'; They use merge-on-read semantics and write positional deletes, see Limitations for UPDATE and DELETE . MERGE INTO The MERGE INTO statement is the recommended way to express ups...express a delete set in the same statement. As with UPDATE and DELETE , MERGE INTO uses merge-on-read semantics and writes positional deletes to the Iceberg table. ALTER TABLE and Schema Evolution The ALTER TABLE statement is supported against Iceberg tabl...ectors Row lineage tracking The biggest change in practice is binary deletion vectors. In v2 tables, DuckDB-Iceberg writes positional deletes as Parquet files; in v3 tables, the same information is encoded as a much more compact binary deletion vector ( Pu... - https://man.mtool.work/duckdb/2.0/core_extensions/iceberg/writing_to_iceberg.htm...
- FROM and JOIN Clauses 9311
- The FROM clause specifies the source of the data on which the remainder of the query should operate. Logically, the FROM clause is where the query starts execution. The FROM clause can contain a single table, a combination of multiple table
...i j k 0 1 1 1 2 3 2 3 5 DuckDB detects when LATERAL joins should be used, making the use of the LATERAL keyword optional. Positional Joins When working with data frames or other embedded tables of the same size, the rows may have a natural correspondence...es or disk files (like CSVs or Parquet files ) do have a natural ordering. Connecting them using this ordering is called a positional join: CREATE TABLE t1 (x INTEGER); CREATE TABLE t2 (s VARCHAR); INSERT INTO t1 VALUES (1), (2), (3); INSERT INTO t2 VALUES...('a'), ('b'); SELECT * FROM t1 POSITIONAL JOIN t2; x s 1 a 2 b 3 NULL Positional joins are always FULL OUTER joins, i.e., the resulting table has the length of the... - https://man.mtool.work/duckdb/2.0/sql/query_syntax/from.html
- Executing SQL in Python 8379
- SQL queries can be executed using the duckdb.sql function. import duckdb duckdb.sql("SELECT 42").show() By default this will create a relation object. The result can be converted to various formats using the result conversion functions. For
...ery Parameters To parameterize a query, pass the values separately from the SQL string using the execute method. Use ? for positional parameters, supplying the values as a list: con.execute("SELECT * FROM integers WHERE i = ?", [42]).fetchall() Named param... - https://man.mtool.work/duckdb/2.0/guides/python/execute_sql.html
- Run Queries 7741
- Overview Because the Go client implements database/sql , queries run through the standard methods: Exec and ExecContext send statements that do not return rows, such as INSERT or DDL, and report the number of affected rows. Query , QueryCon
...holders rather than formatted into the SQL string, which avoids SQL injection and lets DuckDB reuse a plan. DuckDB accepts positional ( ? ) and numbered ( $1 , $2 ) placeholders; pass the values as trailing arguments in order: rows, err := db.QueryContext(... - https://man.mtool.work/duckdb/2.0/clients/go/querying.html
- Run Queries 7741
- Overview A Connection runs SQL through two families of methods: The execute_* methods ( execute() and execute_batch() ) send statements that do not return rows, such as INSERT or DDL, and report the number of affected rows. The query_* meth
...; Binding Parameters Values are bound to a statement's placeholders rather than formatted into the SQL string. DuckDB uses positional ( ? ) and numbered ( ?1 , ?2 ) placeholders. The params! macro packs a heterogeneous list of values into the parameter sli... - https://man.mtool.work/duckdb/2.0/clients/rust/querying.html
- Friendly SQL 7741
- DuckDB offers several advanced SQL features and syntactic sugar to make SQL queries more concise. We refer to these colloquially as “friendly SQL”. Several of these features were first introduced by DuckDB, while some are inspired by other
...using square brackets Simple LIST and STRUCT creation Updating the schema of STRUCT s Join Types ASOF joins LATERAL joins POSITIONAL joins NEAREST joins for top-k similarity search, e.g., over embeddings Trailing Commas DuckDB allows trailing commas , bot... - https://man.mtool.work/duckdb/2.0/sql/dialect/friendly_sql.html
- Unity Catalog Extension 7586
- The unity_catalog extension attaches a Unity Catalog catalog, on Databricks or Unity Catalog OSS, as a DuckDB database. You can list, read, insert into and create its Delta Lake tables. It uses the delta extension to access the tables. For
...lanning again on this attached catalog for 15 minutes. Time travel queries ( AT (...) ) always read through the Delta log. Positional delete files and deletion vectors are applied. A table with equality delete files fails with an error; to read it, attach... - https://man.mtool.work/duckdb/2.0/core_extensions/unity_catalog.html
DuckDB 2.0 Documentation / man.mtool.work