3 people 30dc303f4c fix(db): chunk deleteResolvedReferences IN-list under the SQLite param limit (#1001) (#1023) ...

deleteResolvedReferences bound every id into a single unbounded
`IN (...)`, so a list longer than SQLITE_MAX_VARIABLE_NUMBER (32766 on
the bundled node:sqlite) threw "too many SQL variables" — the one IN-list
in queries.ts that #540 missed. It's reachable only through the exported
QueryBuilder (library use): the internal resolution path uses
deleteSpecificResolvedReferences, which binds per-row and is immune, so
the CLI/MCP indexing pipeline was never affected. Wrap it in the same
SQLITE_PARAM_CHUNK_SIZE loop every sibling query uses, and add a
regression test (33k ids, past the real 32766 ceiling) that throws
without the fix.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-27 14:00:55 -05:00

..

index.ts

perf(resolution): fix O(K²) import-node blowup in "Resolving refs" (#915) (#965)

2026-06-23 11:26:23 -05:00

migrations.ts

fix(cpp): resolve calls through singletons/factories/chained getters (#645) (#742)

2026-06-08 20:18:17 -04:00

queries.ts

fix(db): chunk deleteResolvedReferences IN-list under the SQLite param limit (#1001) (#1023)

2026-06-27 14:00:55 -05:00

schema.sql

fix(cpp): resolve calls through singletons/factories/chained getters (#645) (#742)

2026-06-08 20:18:17 -04:00

sqlite-adapter.ts

fix(resolution): stream node-kind scans in synthesis to fix OOM on dense files (#610) (#653)

2026-06-02 14:23:33 -05:00