Bug #9072 'Max_error_count' system variable cannot be set to zero
Submitted: 9 Mar 2005 15:23 Modified: 1 Apr 2005 21:12
Reporter: Disha Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.11 + 5.0.4 OS:Windows (Windows Server 2003)
Assigned to: Magnus Blåudd CPU Architecture:Any

[9 Mar 2005 15:23] Disha
Even if we set the value of 'Max_error_count' system variable to zero, the effective value for the variable is returned as '1'.

How to repeat:
Repro Steps : 	

1. Connect to the MySQL server as 'root'

2. Set the 'Max_error_count' to zero as follows:
	SET @@Max_error_count=0;
3. Check for the value set for 'Max_error_count'as follows:
	SELECT @@Max_error_count;
Expected Results :  The value returned for 'Max_error_count' should be '0'
Actual Results :    The value returned for 'Max_error_count' is set to '1'

Additional Info:  From the refrence manual: To disable warnings, set max_error_count to 0. In this case, warning_count still indicates how many warnings have occurred, but none of the messages are stored. Thus, 'max_error_count' should be allowed to be set to zero.
[21 Mar 2005 10:07] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

[24 Mar 2005 17:18] Magnus Blåudd
Coe updated according to manual
[1 Apr 2005 21:12] Paul DuBois
Noted in 4.1.11, 5.0.4 changelogs.