and end up fighting, leading to undefined behavior.
There's a saying about assumptions that probably applies here...
On Fri, Jul 12, 2013 at 3:30 AM, Andreas Schwab wrote:
> Jason Sipula writes:
>
> > This fixed bash. So it does appear MySQL is disabling echo.Strange that
>
mysqldump -u someuser -p somedb | mysql -u someuser -p -D someotherdb
>
> so you are saying the password to someuser is somedb and not giving a
> database.
> in the second case you are saying that the password to someuser is -D
>
>
>
> *Gesendet:* Donnerstag, 11. Juli 2013 um
took the time to explain this to me
instead of just blowing me off. Thank you very much.
-Jason
On Thu, Jul 11, 2013 at 11:04 AM, Greg Wooledge wrote:
> On Thu, Jul 11, 2013 at 10:47:12AM -0700, Jason Sipula wrote:
> > I still think this is a bash issue. After the command terminat
like echo is turned off
> try typing
> stty +echo
> when you you say you don't see any output.
> And if its turned off it was probably turned off my mysql.
> *Gesendet:* Donnerstag, 11. Juli 2013 um 19:53 Uhr
> *Von:* "Jason Sipula"
> *An:* Kein Empfänger
> *Cc
something like
> read -sp "Password:" Password
> mysqldump -u someuser --password ${Password} -p somedb | mysql -u someuser
> --password ${Password} -p -D someotherdb
>
> *Gesendet:* Mittwoch, 10. Juli 2013 um 23:54 Uhr
> *Von:* "Jason Sipula"
>
ting the shell prompt on the same line.
Repeat-By:
At the shell, issue the command:
~]# mysqldump -u someuser -p somedb | mysql -u someuser -p -D someotherdb
Shouldn't need to run that command as root, but the mysql user must be
privileged enough to work with the two databases. To simplify things you
can replace "someuser" with root.
Thank you,
Jason Sipula
alup...@gmail.com
