You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: bigint IN/NOT_IN precision loss for values > 2^53
Number(bigint) coercion in matchesFilter lost precision for int64
column values exceeding Number.MAX_SAFE_INTEGER, producing wrong
filter results. Move cross-type equivalents into getInSet() at
cache-build time — integer numbers get BigInt copies, safe-range
bigints get Number copies — so set.has() works directly without
any unsafe coercion on the hot path.
0 commit comments