-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrap migrations in transaction #52
Comments
I like this suggestion. One thing to note, though, is that while this is possible with Postgres, it may not be supported on other popular RDBMS platforms. |
I tested with mysql and sqlite
…On Mon, Jun 24, 2019, 10:28 AM Paul Mestemaker ***@***.***> wrote:
I like this suggestion. One thing to note, though, is that while this is
possible with Postgres, it may not be supported on other popular RDBMS
platforms.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52?email_source=notifications&email_token=AAVSCERAHZYJ57ZGQOFARZTP4BZRXA5CNFSM4HSIAOGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYMA2SY#issuecomment-504892747>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAVSCEUZFJ74U3IUVRG7Z4DP4BZRXANCNFSM4HSIAOGA>
.
|
Looks like MySQL just started supporting Atomic DDL in 8.0. 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Each migration should ideally run in a transaction, to avoid a situation of a migration being partially applied.
The text was updated successfully, but these errors were encountered: