Bug #34838 empty value is allowed for log_output

• Submitted: 26 Feb 2008 13:05
• Modified: 27 Feb 2008 6:48
• Reporter: Rizwan Maredia
• Status: Duplicate
• Category: MySQL Server: Documentation
• Severity: S4 (Feature request)
• Version: 5.1.22
• OS: Any
• CPU Architecture: Any
• Tags: empty value, log_output

[26 Feb 2008 13:05] Rizwan Maredia

Description:
Empty value is allowed where as it is not specified in documentation.

How to repeat:
This is how we can test this issue

Sample Code: 
SET @@global.log_output = "";
SELECT @@global.log_output;

Output: 
SELECT @@global.log_output;
@@global.log_output

Here the output is an empty string.

Suggested fix:
Empty value and its behavior should be documented.

[26 Feb 2008 13:17] Jon Stephens

Not a bug, as http://dev.mysql.com/doc/refman/5.1/en/server-options.html#option_mysqld_log-output clearly states:

"This option determines the destination for general query log and slow query log output. The option value can be given as one or more of the words TABLE, FILE, or NONE. If the option is given without a value, the default is FILE. (For MySQL 5.1.6 through 5.1.20, the default is TABLE.)"

[26 Feb 2008 15:52] Paul DuBois

Previous comment is true for the --log-output option, but not for the log_output system variable.
See Bug#34820.

[26 Feb 2008 19:59] MySQL Verification Team

Thank you for the bug report. Duplicate of bug: http://bugs.mysql.com/bug.php?id=34820

[27 Feb 2008 6:48] Rizwan Maredia

I would suggest that selecting log_output should return FILE even if empty string is assigned to it.