Yep.  File a bug report against the documentation; that table is a
work in progress.  On my system,

[EMAIL PROTECTED] $ /usr/sbin/mysqld --verbose --help | grep warn
  -W, --log-warnings[=#]
                      Log some not critical warnings to the log file.
  -W, --warnings[=#]  Deprecated; use --log-warnings instead.
  --max_error_count=# Max number of errors/warnings to store for a statement.
                      1 = YES = Don't issue an error message (warning only) if
log-warnings                      1
warnings                          1


On Dec 20, 2007 10:24 AM, Martijn van den Burg
<[EMAIL PROTECTED]> wrote:
> Hi Baron,
>
> I know. But that would mean
> http://dev.mysql.com/doc/refman/5.0/en/mysqld-option-tables.html is in
> error, as it says sql_warnings can be set in the option file.
>
>
> Regards,
>
> Martijn
>
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Baron Schwartz
> > Sent: Thursday, December 20, 2007 15:50 PM
> > To: Martijn van den Burg
> > Cc: mysql@lists.mysql.com
> > Subject: Re: How to set 'sql_warnings' in the config file
> >
> > That is not a mysqld option, it's a session variable:
> >
> > mysql> select @@global.sql_warnings;
> > ERROR 1238 (HY000): Variable 'sql_warnings' is a SESSION variable
> >
> > On Dec 20, 2007 9:14 AM, Martijn van den Burg
> > <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > I'm having issues with replication breaking on one machine (Linux,
> > > x64) but continuing normal on the other (Solaris).
> > >
> > > Both run MySQL 5.0.18-standard.
> > >
> > > The only difference betweenn the configuration of teh two is the
> > > setting of sql_notes and sql_warnings.
> > >
> > > I want to find out if that causes the problem. According
> > > http://dev.mysql.com/doc/refman/5.0/en/mysqld-option-tables.html I
> > > should be able to set them in the config file (I'm using
> > > mysqld_multi), but no matter what I use (sql_warnings=0,
> > > sql_warnings=off, change sql_warnings to sql-warnings): every time
> > > mysqld refuses to start, complaining that it does not know
> > the variable 'sql_warnings'.
> > >
> > > How to set sql_notes and sql_warnings at server start up?
> > Did I hit a
> > > bug?
> > >
> > > I am aware that there's a bug in 5.0.18 with the /display/ of the
> > > value of sql_warnings and -notes,
> > > http://bugs.mysql.com/bug.php?id=16195,
> > > could that be related?
> > >
> > >
> > > Regards,
> > >
> > > Martijn van den Burg
> > >
> > > --
> > > The information contained in this communication and any
> > attachments is confidential and may be privileged, and is for
> > the sole use of the intended recipient(s). Any unauthorized
> > review, use, disclosure or distribution is prohibited.
> > Unless explicitly stated otherwise in the body of this
> > communication or the attachment thereto (if any), the
> > information is provided on an AS-IS basis without any express
> > or implied warranties or liabilities.  To the extent you are
> > relying on this information, you are doing so at your own
> > risk.   If you are not the intended recipient, please notify
> > the sender immediately by replying to this message and
> > destroy all copies of this message and any attachments. ASML
> > is neither liable for the proper and complete transmission of
> > the information contained in this communication, nor for any
> > delay in its receipt.
> > >
> > >
> > > --
> > > MySQL General Mailing List
> > > For list archives: http://lists.mysql.com/mysql
> > > To unsubscribe:
> > http://lists.mysql.com/[EMAIL PROTECTED]
> > >
> > >
> >
> >
>
> --
>
> The information contained in this communication and any attachments is 
> confidential and may be privileged, and is for the sole use of the intended 
> recipient(s). Any unauthorized review, use, disclosure or distribution is 
> prohibited.  Unless explicitly stated otherwise in the body of this 
> communication or the attachment thereto (if any), the information is provided 
> on an AS-IS basis without any express or implied warranties or liabilities.  
> To the extent you are relying on this information, you are doing so at your 
> own risk.   If you are not the intended recipient, please notify the sender 
> immediately by replying to this message and destroy all copies of this 
> message and any attachments. ASML is neither liable for the proper and 
> complete transmission of the information contained in this communication, nor 
> for any delay in its receipt.
>
>

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to