Kristen G. Thorson wrote:
But all I really get from this reading is 0 turns it off, 1 prints
some
warnings, and 2 prints level 1 warnings plus aborted connections
warnings. I have not been able to find any additional information
in my
search. Am I missing something, or is this all the docu
> -Original Message-
> From: Colin Charles [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 17, 2007 9:08 PM
> To: Kristen G. Thorson
> Cc: mysql@lists.mysql.com
> Subject: Re: Log Warnings Level
>
> Kristen G. Thorson wrote:
>
> Hi!
>
> > But
Kristen G. Thorson wrote:
Hi!
But all I really get from this reading is 0 turns it off, 1 prints some
warnings, and 2 prints level 1 warnings plus aborted connections
warnings. I have not been able to find any additional information in my
search. Am I missing something, or is this all the doc
On 12 Nov 2005, at 04:26, Harrison Fisk wrote:
The log-warnings option doesn't do what you want. It will cause
the mysqld server log more internal errors. Non-critical errors
such as network disconnects will be logged into the error log with
that setting.
The option you want it is the -
Hi,
On Nov 11, 2005, at 10:01 PM, Marcus Bointon wrote:
At the time I reported this bug back in February: http://
bugs.mysql.com/bug.php?id=8684 I was pleased to see it apparently
fixed so fast. I wasn't yet using MySQL 5, so I couldn't get the
fix. I am now upgrading to 5 using mysql 5.0.1
On 18 Feb 2005, at 16:05, Gleb Paharenko wrote:
There is no direct way to load warnings into log files.
Just for the archives, I reported this as a bug and it's in the MySQL
bug db as having been verified, so I guess now we just hope/wait for a
fix in a later version:
http://bugs.mysql.com/bug.p
Hello.
There is no direct way to load warnings into log files. But you
may use a small value for max_error_count and launch mysql in a
batch mode saving results in the file.
Marcus Bointon <[EMAIL PROTECTED]> wrote:
> I'm migrating a MySQL 3.23 db to 4.1.10 (on Linux x86) and I'm gett
On 18 Feb 2005, at 14:24, Thomas Sundberg wrote:
I would approach this problem by isolating the where the problem
occurs.
I.e. Remove, comment out, half of you insert queries and see if the
problem
still exists. If it does, then remove yet another half of the
remaining part
leaving only 1/4 of t
> -Original Message-
> From: Marcus Bointon [mailto:[EMAIL PROTECTED]
> Sent: den 18 februari 2005 14:47
> To: mysql@lists.mysql.com
> Subject: log-warnings
>
> I'm migrating a MySQL 3.23 db to 4.1.10 (on Linux x86) and
> I'm getting some infrequent warnings when importing data
> dumps
