Skip to content
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

Atomic migrations #1378

Closed
billy1624 opened this issue Jan 9, 2023 Discussed in #1059 · 1 comment · Fixed by #1379
Closed

Atomic migrations #1378

billy1624 opened this issue Jan 9, 2023 Discussed in #1059 · 1 comment · Fixed by #1379
Assignees
Milestone

Comments

@billy1624
Copy link
Member

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)?

@billy1624
Copy link
Member Author

@billy1624 billy1624 self-assigned this Jan 9, 2023
@billy1624 billy1624 mentioned this issue Jan 9, 2023
9 tasks
@billy1624 billy1624 added this to the 0.11.x milestone Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant