Named Parameters

DuckDB supports named parameters written $name. Bind them with execute_with_named, passing (name, value) pairs. Binding is by name, so the order of the pairs is irrelevant.

execute_with_named

execute_with_named(sql, binds: &mut [(&str, &mut dyn AppendAble)]) -> Result<DuckResult>.

use better_duck_core::AppendAble;

let mut id = 7_i32;
let mut name = String::from("bound");
conn.execute_with_named(
    "INSERT INTO t VALUES ($id, $name)",
    &mut [
        ("name", &mut name as &mut dyn AppendAble),   // order does not matter
        ("id",   &mut id   as &mut dyn AppendAble),
    ],
)?;

The value type is the same &mut dyn AppendAble used by positional binding — every DuckValue and the primitive Rust types qualify.

Give the name without the leading $: use "id" to bind $id.

Unknown names are reported

A name that is not a parameter of the SQL is not silently ignored:

use better_duck_core::error::Error;

let mut v = 1_i32;
let err = conn.execute_with_named("SELECT $id", &mut [("missing", &mut v as &mut dyn better_duck_core::AppendAble)]);
assert!(matches!(err, Err(Error::InvalidParameterName(_))));

See Error::InvalidParameterName. An interior NUL in a name is caught as Error::NulError.

Connecting

Querying

Values & Types

Parameters & Statements

Writing Data

Columnar

Concurrency

Interop

Errors & Extensions

User-Defined Functions

Derives & Helpers

execute_with_named

Unknown names are reported

See also

​execute_with_named

​Unknown names are reported

​See also

execute_with_named

Unknown names are reported

See also