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
When we execute the command schema:dump is only migrating the database structure and only the data for the migration table.
I'd like to have more control over the execution of mysqldump (or other database) where I can set if I want to dump the data as well. Can be a new command or a new option --seed where we can have control of the flags
Right now MySqlSchemaState is forcing to "--no-data"
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When we execute the command
schema:dump
is only migrating the database structure and only the data for the migration table.I'd like to have more control over the execution of mysqldump (or other database) where I can set if I want to dump the data as well. Can be a new command or a new option --seed where we can have control of the flags
Right now MySqlSchemaState is forcing to "--no-data"
$this->baseDumpCommand().' --routines --result-file="${:LARAVEL_LOAD_PATH}" --no-data'
Adding that and maybe other options like "--ignore-table" to this command would put it on steroids!
Beta Was this translation helpful? Give feedback.
All reactions