drush sqlq --db-prefix doesn't work any more.

[greg-1-anderson]

Drush 6 behavior (correct):

$ drush sqlq 'select * from users;'
0|||||||0|0|0|0|||0||
1|admin|...|admin@example.com||||1434161704|1434161729|1434161729|1|UTC||0|admin@example.com|b:0;
$ drush sqlq 'select * from {users};'
Error: near line 1: unrecognized token: "{"
Query failed.                                                        [error]
$ drush sqlq 'select * from {users};' --db-prefix
0|||||||0|0|0|0|||0||
1|admin|...|admin@example.com||||1434161704|1434161729|1434161729|1|UTC||0|admin@example.com|b:0;

Drush 7 and Drush 8 behavior:

$ drush sqlq 'select * from users;'
0|||||||0|0|0|0|||0||
1|admin|...|admin@example.com||||1434161704|1434161729|1434161729|1|UTC||0|admin@example.com|b:0;
$ drush sqlq 'select * from {users};' 
Query failed.                                                        [error]
$ drush sqlq 'select * from {users};' --db-prefix

Fatal error: Class 'Drush\Sql\Database' not found in /Users/ga/.composer/vendor/drush/drush/lib/Drush/Sql/SqlBase.php on line 201

Just leaving this here. I'm not really fond of db prefixes myself, but ideally this would still work.

[weitzman]

I see an attempt to prefix in the code. My hunch is that we only don't prefix when an input file is provided (as opposed to a string). I think that other commands use sql-query internally and provide and input file or --file option so they would suffer this same issue. The example given would not fall into this category so no idea on the example shown above.

[greg-1-anderson]

I had a better solution to this problem.

Ideally, Drush would still work with db prefixes, but I don't know if anyone will take the time to circle back here.

[drzraf]

same (blocking) issue drush sql-sanitize which, sadly, will just NOT work without --db-prefix
What to do?

[weitzman]

db prefixes are no longer supported in drush