FA-113 / Storage and queries / Member archive

An exclusion query loses candidates when its subquery contains NULL · case 03

A single unknown exclusion value removes unrelated candidates from an anti-join result.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

For each candidate in input order, retain it unless an excluded non-NULL value is SQL-equal to it. NULL never equals any value, including NULL. Duplicates on the left remain duplicates. Inputs are integers or None.

Why this case matters

Executes real in-memory SQLite three-valued logic to isolate nullable exclusion behavior; this does not simulate a complete database optimizer, concurrent workload, or production query plan.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
unknown exclusion does not poison other values	`[]`	`[4]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.