myco:vault-schema-migration

Safe SQLite schema migration requires applying versioned migrations with idempotent checks to prevent data loss. You add a new migration block, update the SCHEMA_VERSION constant, perform any necessary data backfills, and verify the migration end-to-end in a test vault before deployment.

The best way to handle schema backfills is to include optional backfill steps within your versioned migration block. This ensures new fields are populated correctly while applying safe SQL migrations like ALTER TABLE, preventing data corruption across single-user and multi-device vaults.

Yes, the schema migration process explicitly targets both single-user and multi-device vault deployments. It applies versioned migrations and idempotent checks to ensure data consistency and prevent corruption across all synchronized vault instances during upgrades.

To add a new schema version to the migration chain, you update the SCHEMA_VERSION constants and write a new migration block. This block contains safe SQL statements like ALTER TABLE or CREATE TABLE, including any required backfills, to transition the database safely.

Idempotent checks are required when applying SQL migrations to prevent re-applying migration blocks that have already been executed. This avoids duplicate column errors, data overwrites, and corruption, ensuring safe upgrades across single-user and multi-device vault deployments.