Batch numbers are determined in local run-time instead of by some argument in the migration files.
So, if I initially check out a repository and run the existing migrations from another developer, all the migrations will be of batch 1.
Thus, if I create a new migration, but want to roll it back, all migrations will be rolled back.
Batch numbers are determined in local run-time instead of by some argument in the migration files.
So, if I initially check out a repository and run the existing migrations from another developer, all the migrations will be of batch
1.Thus, if I create a new migration, but want to roll it back, all migrations will be rolled back.