Bug #52239 | Wrong datatype specified for log_output in docs | ||
---|---|---|---|
Submitted: | 20 Mar 2010 5:26 | Modified: | 22 Mar 2010 15:39 |
Reporter: | Shlomi Noach (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | >= 5.1 | OS: | Any |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
Tags: | log_output |
[20 Mar 2010 5:26]
Shlomi Noach
[20 Mar 2010 6:13]
Shlomi Noach
Though, the '' value is disallowed. So this is actually in between ENUM and SET.
[20 Mar 2010 8:23]
Valeriy Kravchuk
Thank you for the problem report. 77-52-28-202:5.1 openxs$ bin/mysql -uroot test Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 5.1.46-debug Source distribution Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> set global log_output='FILE,TABLE'; Query OK, 0 rows affected (0.00 sec) mysql> show global variables like '%output%'; +---------------+------------+ | Variable_name | Value | +---------------+------------+ | log_output | FILE,TABLE | +---------------+------------+ 1 row in set (0.00 sec)
[22 Mar 2010 15:39]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products. "set" is more correct because multiple values are allowed.