Bug #40988 | log_output_basic.test succeeded though syntactically false. | ||
---|---|---|---|
Submitted: | 24 Nov 2008 17:25 | Modified: | 23 Apr 2010 1:51 |
Reporter: | Horst Hunger | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Options | Severity: | S3 (Non-critical) |
Version: | 5.1.30, 6.0.7, 6.0.9-alpha-debug | OS: | Linux (suse-linux-gnu on i686) |
Assigned to: | CPU Architecture: | Any | |
Tags: | disabled |
[24 Nov 2008 17:25]
Horst Hunger
[24 Nov 2008 19:20]
Valeriy Kravchuk
Thank you for a bug report. Verified just as described, also with 5.1.30: C:\Program Files\MySQL\MySQL Server 5.0\bin>mysql -uroot -proot -P3310 test Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 Server version: 5.1.30-community MySQL Community Server (GPL) Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> SET @@global.log_output = ', '; Query OK, 0 rows affected (0.02 sec) Manual (http://dev.mysql.com/doc/refman/5.1/en/server-options.html) clearly says: "The option value can be given as one or more of the words TABLE, FILE, or NONE."
[6 Mar 2010 11:00]
Bugs System
Pushed into 5.5.3-m3 (revid:alik@sun.com-20100306103849-hha31z2enhh7jwt3) (version source revid:vvaintroub@fedora12-20091225154921-x25a5pyw1pxiwobv) (merge vers: 5.5.99) (pib:16)
[23 Apr 2010 1:51]
Paul DuBois
Noted in 5.5.3 changelog. System variables could be set to invalid values.