axiom-database-migration

To add a new column without losing existing user data, use immutable, additive, and idempotent migration patterns. This Skill guides you through safe schema evolution for production SQLite databases, ensuring new nullable columns preserve user data.

A 'cannot add NOT NULL column' error occurs because existing rows lack a default value for the new column. Safe database migration prevents this by applying additive patterns, ensuring schema changes do not violate constraints or crash production apps.

Yes, this database migration approach works with GRDB and SwiftData frameworks for iOS and macOS applications. It provides safe schema evolution patterns tailored to these specific database frameworks to prevent data loss.

The best way to handle FOREIGN KEY constraint failures during database schema changes is to follow strict testing workflows and safe pattern implementation. This Skill addresses common migration errors to ensure stable schema evolution in production environments.

You need idempotent migration patterns when evolving database schemas for production macOS applications with existing user data. These patterns prevent data loss and app crashes by ensuring schema modifications can be applied safely multiple times.