-
Notifications
You must be signed in to change notification settings - Fork 20
Add --single-transaction support for mysql dump #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
--single-transaction
support for mysql dump
JoaRiski
added a commit
that referenced
this issue
Jun 6, 2019
Add support for defining extra parameters to pass to the dump CLI tool, for both the pg_dump and mysqldump Resolves #22
JoaRiski
added a commit
that referenced
this issue
Jun 6, 2019
Add support for defining extra parameters to pass to the dump CLI tool, for both the pg_dump and mysqldump Resolves #22
JoaRiski
added a commit
that referenced
this issue
Jun 7, 2019
Include the --single-transaction mysqldump parameter by default in the configuration object, but allow it to be removed if the extra parameters are defined on the configuration file explicitly. Related to #22
JoaRiski
added a commit
that referenced
this issue
Jun 7, 2019
Include the --single-transaction mysqldump parameter by default in the configuration object, but allow it to be removed if the extra parameters are defined on the configuration file explicitly. Related to #22
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add support for taking the mysql dump with the
--single-transaction
option, as to avoid locking the entire database for the duration of the dump.This could be implemented by adding a section to the
.sanitizerconfig
for extra options to be passed to the dump tool.The text was updated successfully, but these errors were encountered: