Run migrations in a transaction - #4164
Merged
Merged
Conversation
FluentKit's migrator calls `prepare` and then writes the `migrations` row as two separate operations with no enclosing transaction. A multi-step migration that throws part way commits the steps that already succeeded *and* records nothing, so the re-run fails on "column already exists" against a half-changed schema. Add all migrations to an array, and then run each one through a `TransactionalMigration` to force them to run as a transaction. Some migrations (036, 037, 044) already run in transactions, but nesting s safe: Postgres has no nested transactions and FluentKit makes the inner call a passthrough. # Conflicts: # Sources/App/configure.swift
plemarquand
approved these changes
Sep 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rebased branch, supersedes #4135