Precisely, because data migrations are indeed supported, it should be an
option.
Today I'm in other situation, I have a data migration which requires
being run several times (because updates needed data from remote
sources), today I can't do this with an straightforward command.
On 08/26/20
I've always thought flush is a weird command because an empty database is
very normally useless, because of data migrations. The docs do even say:
If you would rather start from an empty database and re-run all migrations,
> you should drop and recreate the database and then run migrate instead.
Currently it's somewhat difficult to process initial data after a flush.
You will need to fake the database state...
In my case I'm creating all tables of the project with the migration
0001 and populating with initial data on migration 0002.
After spending a time looking for solutions found
