Closed (won't fix)
Project:
Drush
Version:
8.x-6.x-dev
Component:
SQL
Priority:
Normal
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
21 Feb 2011 at 14:45 UTC
Updated:
11 Sep 2013 at 04:59 UTC
With Drush 3.x, this command worked:
drush sql-sync ~/httpdocs#default ~/subdomains/dev/httpdocs#default
Is the command line path parameter no longer supported? Must the aliases system be used instead?
Please says it's just a syntax change :-)
Thanks.
Comments
Comment #1
greg.1.anderson commentedI will have to look into this. The path#uri syntax is definitely supported, and I will fix it if it is broken; it is believed to be working.
One thing of note is that bash expands the "~"; it is not recognized by the file system, so in other contexts, it might not work. If you are not typing the above command from the prompt, try using /home/user instead of ~ and see if that works better.
Comment #2
Gabriel R. commentedActually, I am typing the full absolute path starting from / here, the
~/sitesexample was just a shortcut for this report.Just to clarify the use case: we are using sandboxes that we create on a whim to test things, and the path form is very useful here.
PS: I reverted to Drush 3.0 for now, but I am looking forward to all the goodness in 4.x I am already doing a lot of the new things "manually" with my own rsync and drush sqlq commands, so it would be great to have some more automation.
Comment #3
Gabriel R. commentedThis issue is still an issue.
Comment #4
greg.1.anderson commentedThe thing that is broken for me is #default; if I replace this with the uri for the site (/path/to/drupal/#mysite.org), as I have in my site alias, then it works. I tried on master. The later form is preferred, but I'm not sure why #default was rejected.
Try using your site uri as a workaround.
Comment #5
greg.1.anderson 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.