Giorgi / DuckDB.NET / 35474580407

88%

push

github

Bind BigInteger parameters for VARINT columns as BIGNUM

A BigInteger was always sent as a HUGEINT, whatever the parameter type
DuckDB reported, because the converter had no VARINT case. That capped
VARINT parameters at 128 bits: anything wider threw
ArgumentOutOfRangeException from the DuckDBHugeInt constructor, even
though the column would hold it.

Build the value with duckdb_create_bignum from the magnitude bytes and
a sign, so values of any size arrive exactly. DuckDB reports these
parameters as VARINT, so HUGEINT parameters keep the old path.

This also avoids DuckDB's integer to VARINT cast, which drops the top
byte for values from 2^56 to 2^56+182 and for the matching hugeint
range around 2^120 (duckdb/duckdb#25939). Values bound this way are no
longer cast, so they survive on engines that still have the bug.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QEQt5x6WgR3rH3Zsd1guVT

1594 of 1893 branches covered (84.2%)

Branch coverage included in aggregate %.

9 of 9 new or added lines in 2 files covered. (100.0%)

3170 of 3501 relevant lines covered (90.55%)

375098.66 hits per line