MySQL - how to suppress informational messages

[Sysman]

I have a large file containing SQL statements to create a few MySQL tables and it is spitting out a gazillion messages like this:

Query OK, 1 row affected (0.00 sec)

How do I suppress this lot?

I could redirect them to a file, but it's still a lot of processing, and there's 750 MB of input file. Surely there's a simple and low overhead way.

[NickFitz]

I have a large file containing SQL statements to create a few MySQL tables and it is spitting out a gazillion messages like this:

Query OK, 1 row affected (0.00 sec)

How do I suppress this lot?

I could redirect them to a file, but it's still a lot of processing, and there's 750 MB of input file. Surely there's a simple and low overhead way.

OS X | Linux | Other Unix variants:

$verbosescript > /dev/null

Windows | MS-DOS | CP/M:

C:\>verbosescript > NUL

[Sysman]

Thanks Nick. Tons faster, even though it leaves me not knowing whether there were any errors in there. Off to count the INSERTs in the source now

I was hoping for something option to only spit out the errors. ISTR reading about a build option to omit the MySQL stats for every operation but I can't find it right now...

[NickFitz]

Thanks Nick. Tons faster, even though it leaves me not knowing whether there were any errors in there. Off to count the INSERTs in the source now

I was hoping for something option to only spit out the errors. ISTR reading about a build option to omit the MySQL stats for every operation but I can't find it right now...

I would expect it's sending errors to stderr rather than stdout. If so, you can redirect stdout to /dev/null and stderr to a file; it would vary depending on the shell, but I think the bash way of doing that would be something like:

$verbosescript 1> /dev/null 2> errors.txt

EDIT: I just checked in bash, and the above does work for my test - I didn't test with MySQL but I assume it sends error messages to stderr, so that should work.

[Sysman]

I would expect it's sending errors to stderr rather than stdout. If so, you can redirect stdout to /dev/null and stderr to a file; it would vary depending on the shell, but I think the bash way of doing that would be something like:

$verbosescript 1> /dev/null 2> errors.txt

EDIT: I just checked in bash, and the above does work for my test - I didn't test with MySQL but I assume it sends error messages to stderr, so that should work.

And the real answer is that I was trying to use the SOURCE command from the mysql> prompt. If I use the following instead, all those informationals disappear and errors such as "Table already exists" and "Duplicate entry 'xx' for key 'PRIMARY'" are displayed:

$mysql -u username < test.sql

It does conk out straight away if it encounters a syntax error.

Edit: I did this on Windows BTW