From: | "Selena Deckelmann" <selenamarie(at)gmail(dot)com> |
---|---|
To: | "Postgresql PDX_Users" <pdxpug(at)postgresql(dot)org> |
Subject: | silliness with google searches |
Date: | 2008-02-13 00:34:42 |
Message-ID: | 2b5e566d0802121634v3744d3b9xe92c453a26ff9b30@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pdxpug |
By way of Schwern (link is to a thread, i've quoted the first message below):
http://smylers.hates-software.com/2008/02/12/c0df67ed.html
From: Smylers
Date: 13:43 on 12 Feb 2008
Subject: mysqldump Error Messages
$ mysqldump -p -d > current.sql
Hmmm, that didn't prompt me for my password. And it finished very
quickly! Wonder what it did. Let's look in current.sql:
$ cat current.sql
Usage: mysqldump [OPTIONS] database [tables]
OR mysqldump [OPTIONS] --databases [OPTIONS] DB1 [DB2 DB3...]
OR mysqldump [OPTIONS] --all-databases [OPTIONS]
For more options, use mysqldump --help
Nooooooooo!
The whole purpose of having standard error is that it's the _standard_
place for _errors_ to go. Sending error message to standard output is
just hateful.
Smylers
--
Selena Deckelmann
PDXPUG - Portland PostgreSQL Users Group
http://pugs.postgresql.org/pdx
http://www.chesnok.com/daily
From | Date | Subject | |
---|---|---|---|
Next Message | Selena Deckelmann | 2008-02-13 16:04:26 | Extreme Database Makeover: RT -- supplies? |
Previous Message | Selena Deckelmann | 2008-02-12 19:03:42 | Extreme Database Makeover: RT, Meeting 2/21/08 |