It's not obvious the drush sql-sanitize commando is used on live database, the documentation needs clarification what this command actually do.
Here is the help text:
$ drush help sql-sanitize
Run sanitization operations on the current database. You can add more sanitization to this command by
implementing hook_drush_sql_sync_sanitize().Options:
--db-prefix Enable replacement of braces in sanitize queries.
--db-url= >
--sanitize-email= The pattern for test email addresses in the sanitization
operation, or "no" to keep email addresses unchanged. May
contain replacement patterns %uid, %mail or %name.
--sanitize-password=
The password to assign to all accounts in the sanitization
operation, or "no" to keep passwords unchanged.Aliases: sqlsan
The description is assuming the user understand what "sql sanitization" mean, not everyone does. I know what "sql sanitization" means, but without further description or context I got confused what this command is for based on the description alone.
I question in what instances does anyone expect this to be default behavior, and in what instances is it useful to sanitize a live database? Wouldn't it be more useful and much more safer to do a sanitized database dump by default, and requiring extra argument to do changes directly on live database (if that what you really wanted to do)?
I am using Drush 8.0-dev. Thanks in advance and have a good day.
Comments
Comment #1
helmo commentedThis issue was marked closed (won't fix) because Drush has moved to Github.
If desired, you may copy this bug to our Github project and then post a link here to the new issue. Please also change the status of this issue to closed (duplicate).
Please ask support questions on Drupal Answers.