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

greg.1.anderson’s picture

Assigned: Unassigned » greg.1.anderson

I 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.

Gabriel R.’s picture

Actually, I am typing the full absolute path starting from / here, the ~/sites example 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.

Gabriel R.’s picture

This issue is still an issue.

greg.1.anderson’s picture

Title: sql-sync with paths as CLI parameters » Site selection /path/#default does not work for #default (sql-sync with paths as CLI parameters)
Category: support » bug

The 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.

greg.1.anderson’s picture

Version: All-versions-4.2 » 8.x-6.x-dev
Status: Active » Closed (won't fix)
Issue tags: +Needs migration

This 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.