Unable to import database with `drush sql:cli < foo.sql`

[TMWagner]

Updated dev environment to Drush 9.6.0-beta; Unable to load (import from dump file) database.

executed command drush sqlc < databasedump.sql

Expected database to load

Actual behavior
command took me to MySQL command line

System Configuration

Q	A
Drush version?	9.6.0-beta
Drupal version?	8.6.5
PHP version	7.2.13
OS?	Mac

Additional information
Add any other context about the problem here.

[weitzman]

Our betas as numbered. Which beta are you using?. Its reported in drush status

[weitzman]

OK, I can reproduce this on master branch. Will investigate.

[weitzman]

We have found an ugly fix for sql:cli by adding this snippit:

        stream_set_blocking(STDIN, 0);
        // The number below was chosen arbitrarily but seems to matter.
        if (fgets(STDIN, 4096)) {
            $process->setInput(STDIN);
        }
        else {
            $process->setTty(true);
        }

Until we merge that or find a better way, I suggest you use sql:connect instead of sql:cli. See the Usage examples in its help.

[weitzman]

I looked at our other usages of commands reading from stdin and they all are unaffected by this problem, because they start reading based on an argument value of - (state:set, cache:set, config:set, ...). So we can fix this command to behave as it has, or we can point people to drush sql:connect < foo.sql as a replacement (via a helpful Exception). sql:connect been the documented way to do this for a long time.

I'm having the same issue on Drush Commandline Tool 9.7.1 in my Cloud9 (Amazon Linux AMI) environment.
./vendor/bin/drush sqlc < dump.sql is entering the mysql mode instead of piping the dump.sql into it.
This commit is working for me: 9a03ed8

[wah22]

So I am using drush 10.2.0 and drush sqlc < test.sql doesn't work. It takes me into the mysql command prompt

[tomdearden]

So I am using drush 10.2.0 and drush sqlc < test.sql doesn't work. It takes me into the mysql command prompt

Same here on Drush 9.7.2 - this used to work on Drush 8, FWIW - as did piping from gunzip -c for compressed archives. Both now dump out to a MySQL client command prompt. Using the string output from drush sql-connect in place of the drush sqlc command works as a workaround but I miss the elegance of the old way of doing it :(

[rsanzante]

It seems the fix was never committed.

The two commits (#3859 (reference) and #3859 (reference)) are not in the repository. If you check the commit's page (9a03ed8 and b67442d) you can see the following message:

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Indeed, the git hashes are not in git:

$ git o 9a03ed8
error: pathspec '9a03ed8' did not match any file(s) known to git  

$ g o b67442d
error: pathspec 'b67442d' did not match any file(s) known to git     

Both commands were run against a fresh clone of git@github.com:drush-ops/drush.git.

Last, the merge referenced (#3865) does not modify the src/Commands/sql/SqlCommands.php file.

I've tested the code proposed in the cli function in that file:

    public function cli(InputInterface $input, $options = ['extra' => self::REQ])
    {
        $sql = SqlBase::create($options);
        $process = $this->processManager()->shell($sql->connect(), null, $sql->getEnv());
        if (!Tty::isTtySupported()) {
            $process->setInput($this->stdin()->getStream());
        } else {
            $process->setTty($this->getConfig()->get('ssh.tty', $input->isInteractive()));
        }
        $process->mustRun($process->showRealtime());
    }

However, is not clear to me if we should use this code or the "new StdinAwareInterface" as it is said on the merge request above.

In my case, the problem arises using "CentOS Linux release 7.6.1810 (Core)".

[rsanzante]

@greg-1-anderson, you may be interested in my previous comment as you were the author of the commit that was never committed (or that's what it seems).

[bioshazard]

@rsanzante, I ran into a similar issue recently. I thought I had broken something in my container environment, but applying the diff you linked here, 9a03ed8, I am able to utilize sqlc with STDIN as expected in 10.3.6 provided by the latest composer require drush/drush:10.x. I will search for an open issue and if not, maybe open a fresh one with this thread as a reference. Thanks for reporting your findings. For now, I plan to workaround this trouble by adding this patch in on a hard coded 10.3.6 composer target: https://github.com/drush-ops/drush/commit/9a03ed80412fd1c2113fd8392c50b1846bd5ef2e.patch