-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Sanitize command separate from sql-sync #89
Comments
We actually already have We should probably just unhide it. |
I have no strong feeling on unhiding. We discussed this at https://drupal.org/node/1112142 |
Awesome! I searched the codebase before posting but missed it. Grr. Would be a great one to unhide (from my perspective anyway). |
Merged
kostajh
pushed a commit
to kostajh/drush
that referenced
this issue
Nov 26, 2013
As per drush-ops#89 (comment), unhiding sql-sanitize from help.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think it would be useful to be able to sanitise a site without having to sql-sync. For example, let's say I have 30 compressed database backups (not sanitised — they're backups) and I want to use one on my dev site. I don't want to hit the live site for a fresh dump using sql-sync as that's heavy on the server.
To get this into my dev unsanitised I simply do:
To do this sanitised I have to use sql-sync, which has two problems:
a) can't take a gzipped dump file, so I have to gunzip it first somehow
b) needs me to
which is counterintuitive and seems to be redundantly dumping @dev to an .sql file then restoring it straight back, which takes quite a while on a large db.
I would love to be able to do:
The text was updated successfully, but these errors were encountered: