Currently the tool is designed to be used piping the output to a file like so mysqldump -u yada -pbadpass -h db | anonymize-mysqldump --config config.json > anonymized.sql. This causes an issue where any errors/notices are also piped to the resulting file.
Would it be better to have a default path to output the file to, which can be overridden or require an output path in the command? Perhaps like mysqldump -u yada -pbadpass -h db | anonymize-mysqldump --config config.json -o anonymized.sql?
Currently the tool is designed to be used piping the output to a file like so
mysqldump -u yada -pbadpass -h db | anonymize-mysqldump --config config.json > anonymized.sql
. This causes an issue where any errors/notices are also piped to the resulting file.Would it be better to have a default path to output the file to, which can be overridden or require an output path in the command? Perhaps like
mysqldump -u yada -pbadpass -h db | anonymize-mysqldump --config config.json -o anonymized.sql
?