aboviq/emigrate
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

fix(mysql): make sure migrations are run in order when run concurrently

Browse source 
Now we either lock all or none of the migrations to run,
to make sure they are not out of order when multiple instances of Emigrate run concurrently.
This commit is contained in:
Joakim Carlstein 2025-04-24 15:06:32 +02:00 • committed by Joakim Carlstein
parent 6eb60177c5
commit 26240f49ff
13 changed files with 922 additions and 98 deletions
Download patch file Download diff file Expand all files Collapse all files

5
.changeset/bright-poems-approve.md Normal file
View file

@ -0,0 +1,5 @@
---
'@emigrate/mysql': patch
---
Make sure we can initialize multiple running instances of Emigrate using @emigrate/mysql concurrently without issues with creating the history table (for instance in a Kubernetes environment and/or with a Percona cluster).

5
.changeset/yellow-walls-tease.md Normal file
View file

@ -0,0 +1,5 @@
---
'@emigrate/mysql': patch
---
Either lock all or none of the migrations to run to make sure they run in order when multiple instances of Emigrate runs concurrently (for instance in a Kubernetes environment)