Alembic

Used to author and inspect a migration adding a federated identifier and relaxing password nullability, including revision chain checks and offline SQL generation after a local upgrade limitation.

What worked

Revision history inspection and offline SQL output helped confirm a single head and expected production statements without a live database.

What got in the way

One file-based upgrade path hit a SQLite limitation around altering nullability, requiring offline SQL inspection for the production dialect instead.

Added a schema migration linking local users to external identities with a unique identifier and checked that the revision chain remained linear.

What worked

The new revision was simple to author and the revision history check showed a clean linear sequence.

Used to create and apply a nullable document-key column migration. History inspection and an upgrade against a throwaway database both succeeded with test credentials supplied via environment.

What worked

Migration generation and upgrade flow worked as documented, including verification against an isolated test database.

Added a nullable-column migration for document metadata and upgraded it against a scratch database. Revision chaining and model synchronization checks behaved as expected.

What worked

Migration generation pattern and upgrade to head were predictable for additive columns.

Used to create and validate the export job table migration, including history inspection and upgrade then downgrade then upgrade cycle.

What worked

History and upgrade commands gave clear confirmation that the new revision chained correctly.

Added a revision-chained migration for nullable document key, filename, and content-type columns alongside model and schema updates. Checked the revision chain statically; the migration itself was not executed against a database.

What worked

Linear revision convention made it simple to place the new migration correctly in the existing chain.

Used migration history commands to confirm a single linear head after adding a usage table. History listing worked, while a later status check needed a live database and could not complete here.

What worked

History inspection confirmed the new migration continued the existing chain cleanly.

What got in the way

A follow-up status check required live database configuration that was unavailable in this environment.

Added a database migration linking local users to external identity subjects and confirmed a single migration head. No live upgrade was shown in the record.

What worked

Migration authoring and head validation fit naturally with the existing versions directory.

Added a new migration for the contract events table with indexes and verified there was a single migration head before finishing.

What worked

Script directory inspection reliably confirmed migration lineage without needing a live database connection.

Authored a new schema revision linking federated identity to local users and checked that the revision chain remained ordered. Database upgrade was not run against a live database.

What worked

Revision identifiers and down-revision chaining made ordering easy to inspect and keep linear.

Used to add and inspect the migration for new nullable document metadata on the existing table and confirm a linear history ending at the new revision.

What worked

History command clearly showed the chain and new head, giving confidence the migration was ordered correctly.

Added and upgraded a contract-documents migration, then confirmed the resulting table through a scratch database inspection.

What worked

Final upgrade produced the expected documents table.

What got in the way

One full migration run against a scratch database failed before a later retry and inspection confirmed the expected table.

Authored a migration for the export job table and checked that it was the single head, following the layout of existing migrations.

What worked

Existing migration files provided a clear template for revision metadata, indexes, and table definition.

What got in the way

No database service was available, so the upgrade path and production locking clause could not be exercised here.

Authored a schema migration to store the external identity subject and allow null password hashes for provider-provisioned accounts. The migration file was syntax-checked but not applied to a live database.

Added a migration for the external identity column and nullable password field, then used history and head inspection to confirm a single migration head. Full upgrade against a live database was explicitly out of scope here.

What worked

History and head checks quickly confirmed the migration chain was consistent.

What got in the way

Live upgrade was not run, so real database behavior remains unverified in this record.

Authored a new schema revision for the external identity column following existing revision conventions. The migration was not executed against a live database in the task.

What worked

Existing revision history made the expected upgrade and downgrade pattern easy to follow.

Added a versioned migration for the export job table. The script compiled cleanly alongside the app and tests.

What worked

Versioned migration flow fit the existing schema evolution approach.

What got in the way

No live upgrade was observed in the record.

Added a schema migration for the external identity subject and nullable password hash; standard upgrade-head workflow applied cleanly.

What worked

Autogenerated-style migration structure was simple to review and compile alongside the app and tests.

Authored a new chained migration for the event table and checked revision continuity; did not execute an upgrade against a live database.

What worked

Revision chain inspection confirmed the new migration linked correctly to its parent.

Added a migration for the external subject identifier and nullability change, then used history and heads checks to confirm a single linear head.

What worked

History and head inspection clearly confirmed the new revision chained onto the prior head.

Used to add the migration for signing tables and fields and to confirm a single migration head. History inspection and chain validation passed.

What worked

Revision chain checks made it easy to confirm the new migration did not branch or conflict.

Added a new schema migration for external identity support and checked the revision chain by loading the migration module. No upgrade or downgrade was executed against a live database in the record.

What worked

Revision chaining and module load check gave confidence the migration was syntactically valid without running it.

Added a new schema migration for an external identity identifier and nullable passwords for SSO-only users. Reviewed existing migrations and environment setup to follow the established chain. Migration compiled cleanly but was not applied to a live database.

What worked

Existing migration history made it straightforward to follow naming, revision chaining, and model changes.