Frontmatter
| id | 9757 |
| title | [AI] Accelerate Vector DB Migration & Recreate Topology Wipe |
| state | Closed |
| labels | enhancementaibuild |
| assignees | tobiu |
| createdAt | Apr 7, 2026, 4:10 PM |
| updatedAt | Apr 7, 2026, 4:12 PM |
| githubUrl | https://github.com/neomjs/neo/issues/9757 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Apr 7, 2026, 4:12 PM |
[AI] Accelerate Vector DB Migration & Recreate Topology Wipe
Closedenhancementaibuild
tobiu assigned to @tobiu on Apr 7, 2026, 4:11 PM
tobiu
Apr 7, 2026, 4:11 PM
Task completed. The destructive SQLite unlink error has been natively refactored to use GraphService.db.storage.clear() preventing full purges. The historical database matrices have been successfully extracted and reimported, and DreamService correctly resumes its high-latency topological ingestion framework.
tobiu closed this issue on Apr 7, 2026, 4:12 PM
Problem
The recent shift from ChromaDB to Native Neo SQLite introduced bugs in the graph destruction utility (
recreateGraphDb.mjs), causing the overarching shared SQLite container (memory-core.sqlite) to be unlinked. This accidentally purged non-graph episodic memories. Additionally, the fallback rescue migration script relied heavily on high-latency LLM inference.Solution
recreateGraphDb.mjshas been firmly refactored to utilize internal native.clear()functions viaGraphServiceto flush Node/Edge logic precisely without dropping vector storage.Ollama.embedTextbottlenecks by piping matrix float arrays natively from the legacy Chroma SQLite binary blob directly to the unified tabularSQLiteVectorManager.