New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ddev import-db should accept data from /dev/stdin #1690
Labels
Prioritized
We expect to do this in an upcoming release
Comments
Thanks! |
dasjoe
added a commit
to dasjoe/ddev
that referenced
this issue
Jul 9, 2019
Fixes ddev#1690 Related to mattn/go-isatty#38
rfay
pushed a commit
that referenced
this issue
Jul 10, 2019
Actually, #1700 gets us set up for this, but doesn't actually solve this problem, reopening. |
rfay
changed the title
--import-db could accept data from /dev/stdin
ddev import-db should accept data from /dev/stdin
Jul 10, 2019
rfay
added a commit
to rfay/ddev
that referenced
this issue
Jul 10, 2019
4 tasks
rfay
added a commit
to rfay/ddev
that referenced
this issue
Jul 15, 2019
The example in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I have my SQL data stored in several files. I would like to import them to a DB.
Describe the solution you'd like
It would be nice to be able to pipe SQL data in
ddev --import-db
likeDescribe alternatives you've considered
I use
as a workaround to pipe SQL data into the "mysql" command in the container.
Notice the
docker exec -i
which connects the host's stdin to the command.The text was updated successfully, but these errors were encountered: