---
id: 10463
title: 'Bug: Memory Core SQLite hits parameter limit during massive GraphLog syncs'
state: CLOSED
labels:
  - bug
  - ai
assignees: []
createdAt: '2026-04-28T08:57:11Z'
updatedAt: '2026-04-28T09:00:04Z'
githubUrl: 'https://github.com/neomjs/neo/issues/10463'
author: neo-gemini-pro
commentsCount: 0
parentIssue: null
subIssues: []
subIssuesCompleted: 0
subIssuesTotal: 0
blockedBy: []
blocking: []
closedAt: '2026-04-28T09:00:04Z'
---
# Bug: Memory Core SQLite hits parameter limit during massive GraphLog syncs

## Problem
The `Memory Core` crashes with a "too many SQL variables" error during `syncCache` operations. This happens because the SQLite `IN (...)` clause has a hard limit of 999 parameters, which is easily exceeded when the `runSandman` extraction pipeline generates thousands of graph mutations (Tri-Vector concepts).

## Solution
Implement a chunking mechanism in `SQLite.mjs` (in `getDeltaLog`, `loadNodeVicinitySync`, and related methods) to slice parameter arrays into batches of 400. This gracefully resolves the crash and allows the Memory Core to scale securely against massive edge mutations.

Authored by Gemini 3.1 Pro (Antigravity).

## Timeline

- 2026-04-28T08:57:13Z @neo-gemini-pro added the `bug` label
- 2026-04-28T08:57:13Z @neo-gemini-pro added the `ai` label
- 2026-04-28T08:57:37Z @neo-gemini-pro cross-referenced by PR #10464
- 2026-04-28T09:00:04Z @tobiu referenced in commit `dc6a2d7` - "fix(ai): implement SQLite chunking and restore Tri-Vector pipeline (#10463) (#10464)

Co-authored-by: tobiu <tobiasuhlig78@gmail.com>"
- 2026-04-28T09:00:05Z @tobiu closed this issue
- 2026-04-28T09:00:05Z @neo-gemini-pro referenced in commit `a72d70f` - "fix(ai): implement SQLite chunking for bridge-daemon to fix A2A substrate (#10463)"
- 2026-04-28T09:22:54Z @neo-opus-ada cross-referenced by PR #10466
- 2026-04-28T09:37:30Z @neo-opus-ada cross-referenced by #10467
- 2026-04-28T10:41:52Z @neo-opus-ada cross-referenced by #10469
- 2026-04-29T10:05:53Z @neo-gemini-pro cross-referenced by #10484

