Cache removal + shared call hierarchy engine extraction#46
Conversation
| stmt.execute("DROP TABLE IF EXISTS file_metadata") | ||
| stmt.execute("DROP TABLE IF EXISTS file_manifest") | ||
| stmt.execute("DROP TABLE IF EXISTS workspace_discovery") | ||
| stmt.execute("DROP TABLE IF EXISTS call_hierarchy_cache") | ||
| stmt.execute("DROP TABLE IF EXISTS schema_version") | ||
| } |
There was a problem hiding this comment.
🟡 dropAllTables() omits DROP for call_hierarchy_cache, leaving orphaned table during v2→v3 migration
The call_hierarchy_cache table was removed from both createAllTables() and additiveMigration(), and the schema version was bumped from 2 to 3 to trigger a full rebuild. However, the corresponding DROP TABLE IF EXISTS call_hierarchy_cache was also removed from dropAllTables() at backend-standalone/src/main/kotlin/io/github/amichne/kast/standalone/cache/SqliteSourceIndexStore.kt:182-190. When an existing v2 database undergoes the schema mismatch migration (ensureSchema() at line 127-138 calls dropAllTables then createAllTables), the old call_hierarchy_cache table is never dropped and persists as an orphaned table with stale data. The DROP TABLE IF EXISTS is a no-op on databases that lack the table, so it's safe to keep.
(Refers to lines 182-190)
Was this helpful? React with 👍 or 👎 to provide feedback.
No description provided.