new-migration

To add a new SQLite schema migration, first check the current version, write failing tests for the new tables or columns, implement the SQL changes in storage.py, and add corresponding storage methods to make the tests pass.

Managing SQLite database schema evolution involves applying a structured, versioned system to update storage.py, ensuring new tables or columns are guided by failing tests before implementing the actual SQL changes.

You test SQLite migrations by writing failing tests first to define expected behavior, then implementing the SQL schema changes and storage methods until those tests pass, ensuring reliable database updates.

Yes, you need to manually update storage.py by adding the new SQL schema changes and corresponding Python storage methods, guided by a test-driven approach to ensure the database updates are robust.

You should use a test-driven approach for SQLite schema migrations whenever adding new features that require new database tables or columns, ensuring changes are reliable and safely integrated into storage.py.

Updating an SQLite schema without breaking existing methods requires checking the current version and writing failing tests first, then implementing SQL changes and adding new storage methods to maintain robustness.