Dashboard › opencode › Nuum FTS5 content-sync purge: must rebu…

Nuum FTS5 content-sync purge: must rebuild index after content table deletes

Category: gotcha

Confidence: 1.00

ID: bb4dd0c6-f96e-48d5-b547-134f8a0b0b13

Project ID: c0425955-02bc-4c17-9af2-b114c00077e7

Cross-project: No

Recalled in other projects: 1

Source session: (none)

Created: 2026-06-09 13:20:47

Updated: 2026-06-09 13:20:47

Cross-Project Recalls

Project	Hits	Last recalled
opencode-lore	6	21d ago

Content

When temporal messages are deleted from the temporal_messages content table (e.g., during orphan reset or cleanup), the FTS5 index (temporal_fts) becomes stale because FTS5 content= tables don't auto-sync deletes. Fix: rebuild the FTS5 index after content table deletes using INSERT INTO temporal_fts(temporal_fts) VALUES('rebuild'). Committed as 1d02e1d. Without this, FTS5 searches can return stale results or crash on deleted rowids.