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
I have no detailed experience with that flag, e.g. I don't know if there are drawbacks or collisions with other flags. I just wondered if it might be worth supporting?
I think I'll give the command a try as is, maybe it doesn't matter. I just definitely know, that our largest tables wont fit in RAM if that's required for the dump command without --quick.
The text was updated successfully, but these errors were encountered:
Related to #461
Add support for the --quick option in the project database dump command.
* Add a new flag `--quick` to the `projectDatabaseDumpCmd` command.
* Pass the `--quick` option to the `database.NewMySQLDumper` function when the `--quick` flag is set.
* Update the list of supported options in `cmd/project/project_database_dump.go` to include the `--quick` option.
* Modify the `cmd/project/project_database_dump.go` file to handle the `--quick` flag and pass it to the database dumper.
---
For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/shopware/shopware-cli/issues/461?shareId=XXXX-XXXX-XXXX-XXXX).
Hi,
I'm about to dump a rather large database, with sizes per table up to 9gb and did some research, if that can affect the production system.
I came across the --quick option for mysqldump: https://dev.mysql.com/doc/refman/8.4/en/mysqldump.html#option_mysqldump_quick
And it seems like the underlying go lib here supports that flag as well? https://github.com/doutorfinancas/go-mad/blob/master/database/option.go#L22-L23
I have no detailed experience with that flag, e.g. I don't know if there are drawbacks or collisions with other flags. I just wondered if it might be worth supporting?
I think I'll give the command a try as is, maybe it doesn't matter. I just definitely know, that our largest tables wont fit in RAM if that's required for the dump command without --quick.
The text was updated successfully, but these errors were encountered: