Closed (won't fix)
Project:
Drush
Version:
8.x-6.x-dev
Component:
Core Commands
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Nov 2011 at 23:24 UTC
Updated:
11 Sep 2013 at 11:51 UTC
When using an alias file dumping from a remote database to a local one, if %dump path is specified, drush fails to overwrite an existing dump file and imports the old file, from the first good dump. All subsequent imports will import that first dump.
Happens across sites.
If you change the name of the dump file in the alias file, drush imports the correct dump. That means it's not a permissions issue.
I found a temporary workaround by hacking the module.
Remove the if statement from sync.sql.inc on line 185 so that this
if ($source_settings['dump-is-temp']) {
$source_rsync_options['remove-source-files'] = TRUE;
}
becomes this:
$source_rsync_options['remove-source-files'] = TRUE;
Don't like that but it does the job. I can't find a cli switch for this option. Hoping somebody smarter than me will fix it!
Comments
Comment #1
greg.1.anderson commentedPerhaps the option you are looking for is --no-cache. It would not be a good idea to make the change suggested above; deleting non-temp files subverts the cache option and the fast rsync behavior that overwriting an existing dump file provides.
Comment #2
moshe weitzman commentedPlease reopen as needed.
Comment #3
glass.dimly commentedThe comment in #1 addresses my workaround, but not the issue itself.
Re-opening.
Comment #4
greg.1.anderson commentedHave you tried the --no-cache option?
Comment #5
greg.1.anderson commentedThis issue was marked
closed (won't fix)because Drush has moved to Github.If you still need help, please ask your question again on Drupal Answers and then post a link here to the new question. Please also change the status of this issue to
closed (duplicate).Use our Github project for contributing code, or reporting bugs, or requesting features.