Cross platform and list-length boundaries for DuckDB BIGNUM lambdas
A scalar control is insufficient to approve lambda comparisons involving a large negative number. Check result Booleans across list lengths and element positions on the operating system that will run the query.
Cross platform and length boundaries
Large-integer comparison tests should cross both platform and list-length boundaries. A working scalar comparison on a development Mac does not establish the multi-element Linux path. Truthound Core can check the exported Boolean outcomes against exact integer order. [1, 2, 3]
A Linux lambda report
DuckDB issue #28044 reports a negative BIGNUM string constant behaving as though its sign were reversed inside a Linux 2.0 list lambda with at least two elements. Single-element, outside-lambda, and macOS controls have different outcomes in the report. [1]
Use the operating platform
Use the same large negative constant in scalar, one-element, and multi-element paths on the operating system actually deployed. Preserve each list position and Boolean result. Do not narrow the BIGNUM to fixed-width integer or float merely to construct the inspection table. [1, 3]
Sign establishes the reference
For positive 12345 and negative -(10^100), sign alone proves 12345 > -(10^100). At the 12345 position, true passes; false fails even if the single-element control succeeds. This is an exact-order fixture rather than a floating tolerance comparison. [1, 3]
Separate exact arithmetic from checking
ColumnPairValidator in Truthound Core Python SDK 3.3.2 compares non-null result Booleans with the prepared reference. Arbitrary-precision evaluation belongs in input preparation. The SDK does not certify all platforms or identify a memory-corruption cause from the outcome table. [1, 2, 3]
Limit approval to tested combinations
Keep an arbitrary-precision reference and an outside-lambda control, and limit approval to tested platform/version combinations. A broad engine upgrade needs its own evidence across those paths. [1, 3]
Record the failing position
A useful failure record names the position, list length, platform, and expression context. That avoids reducing a path-dependent sign error to a generic claim that the large number itself is unsupported. [1, 3]
Application conditions
Prepare scalar and list-length outcomes for the same BIGNUM constant on the operating OS.
Alternatives
Retain an arbitrary-precision reference and an outside-lambda control.
Limitations
Do not narrow to fixed-width integers or floats, or generalize one platform’s success.
Evidence
- Event checked
- Subject checked
- Modified
