You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by gd87429 September 23, 2022
If you run Migrator::up() in parallel (like when you spin up multiple servers), is there a chance the same migration might run more than once?
If yes -- are there plans to build-in support for atomic migrations, or should the user make sure migration cannot be applied twice (like checking if data exists before seeding the table)?
The text was updated successfully, but these errors were encountered:
Discussed in #1059
Originally posted by gd87429 September 23, 2022
If you run
Migrator::up()
in parallel (like when you spin up multiple servers), is there a chance the same migration might run more than once?If yes -- are there plans to build-in support for atomic migrations, or should the user make sure migration cannot be applied twice (like checking if data exists before seeding the table)?
The text was updated successfully, but these errors were encountered: