Repository navigation
v0.3.0
Builds against DuckDB 2.0.0 as well as the pinned v1.5 line.
- DuckDB 2.0 compatibility.
CompatNameis derived fromtable_function_bind_t's fourth parameter with astatic_assertpinning it, rather than probed for with__has_include—identifier.hppwas backported intov1.5-variegatawithout the accompanying signature change, so a header-presence probe returns the wrong answer as soon as pins advance. All fourCatalog::GetEntrycall sites are wrapped, including the templated one inBindApplyWith, along with thechild_list_tkeys and theFunctionExpression/BindScalarFunctionname sites. - The security model is documented. Modes (
none/blacklist/whitelist/validator) and thefunc_apply_set_*functions existed but were absent from the README, with the default beingmode = "none"— no restrictions. The function table was also incomplete: it namedvalidatoras a mode with no documented way to set it. - A README example that never worked is fixed.
apply_table_with('generate_series', args := [1], kwargs := {stop: 10, step: 2})errored on every version that shipped it —stop/stepare positional parameters, andkwargsis not a keyword-flavoured way to spell them. Replaced with examples that run, plus the first passing tests forapply_table_with's kwargs; the only prior case asserted a failure. - Return-type behaviour documented, including that
VARCHARis the fallback when a constant name fails bind-time lookup, not only for dynamic names.
Verified on both lines: main CI green, and the DuckDB-main canary's Build and Test steps both passing — this repo's first green canary on main.