Bug #16521 | Events: mysql.event.on_completion value is 'DROP' | ||
---|---|---|---|
Submitted: | 15 Jan 2006 22:15 | Modified: | 14 Feb 2006 19:41 |
Reporter: | Peter Gulutzan | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.1.6-alpha-debug | OS: | Linux (SUSE 10.0) |
Assigned to: | Andrey Hristov | CPU Architecture: | Any |
[15 Jan 2006 22:15]
Peter Gulutzan
[16 Jan 2006 11:14]
MySQL Verification Team
Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 5.1.6-alpha-debug Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> create event e_63 on schedule every 1 second on completion not preserve -> do set @a=5; Query OK, 1 row affected (0.03 sec) mysql> select on_completion from mysql.event where name = 'e_63'; +---------------+ | on_completion | +---------------+ | DROP | +---------------+ 1 row in set (0.01 sec)
[18 Jan 2006 16:06]
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: http://lists.mysql.com/commits/1276
[19 Jan 2006 16:15]
Sergei Golubchik
I don't think it's a bug - nowhere in the manual we promise that the content of the mysql.* tables will match exactly what you've typed. E.g. you write GRANT ... TO user@host but there's no '@' character in mysql.user table.