myco:vault-schema-extension

To keep SQLite vault and Cloudflare D1 schemas in sync, apply versioned, idempotent migrations that support new tables, backfill-safe ALTERs, and D1's lazy-migration behavior. This ensures local and cloud database representations stay aligned during feature evolution.

Safe schema migrations on Cloudflare D1 require idempotent changes with guards like IF NOT EXISTS. You must account for D1's lazy-migration behavior by applying defensive patterns that prevent partial deployments and maintain cross-database consistency with SQLite.

To add FTS indexes to SQLite and mirror them to D1, create the FTS index and set up triggers within your versioned migration. This ensures both the local SQLite vault and the Cloudflare D1 schema maintain full-text search alignment.

Yes, you can evolve existing SQLite and D1 schemas using backfill-safe ALTER statements within idempotent migrations. This approach safely modifies table structures without breaking existing data integrity or cross-database synchronization.

You need to update query modules after a schema migration to reflect structural changes like new tables or altered columns. This ensures application queries correctly target the updated schema in both the local SQLite vault and Cloudflare D1.

D1 lazy migrations can cause partial deployment states where the cloud schema lags behind local SQLite. To overcome this limitation, use versioned migrations with defensive patterns and guards to enforce cross-database consistency.