feat(storage): versioned schema migrations - #48
Merged
Conversation
- New storage/migrate.go: Migration framework with 5 migrations (initial schema, indexes, node_metadata, embeddings_hnsw, encryption columns) - storage/sqlite.go: Simplified createTables() to only create schema_version + initial schema; calls Migrate() for remaining - Integrity check + process lock acquired after migrations - TestProcessLock verifies cross-process locking
CI triage on PR #48. lock.go carries the error-handling fix from the process-lock branch ahead of merge.
…72,6089,6090,6091,6218})
- lock_unix.go/lock_windows.go carried over from the process-lock PR so windows builds pass (lock.go was unix-only) - check tx.Rollback error in migrate.go CI triage on PR #48.
# Conflicts: # storage/sqlite.go
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 1 SQLite hardening (2/5). Merges after #47.
storage/migrate.gowith aschema_versiontable and ordered, idempotent migrationscreateTables()now applies the base schema only; later changes are migrationsnode_metadataandembeddings_hnswtables plus encryption columnsMerge order: after process-lock (#47).