MySQL Bugs: #22662: Inconsistent values displayed for event

Bug #22662	Inconsistent values displayed for event_scheduler when set to DISABLED
Submitted:	25 Sep 2006 10:47	Modified:	28 Sep 2006 14:01
Reporter:	Jon Stephens	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Stored Routines	Severity:	S3 (Non-critical)
Version:	5.1.12-bk	OS:	Linux (SUSE 10.0)
Assigned to:	Andrey Hristov	CPU Architecture:	Any

Description:
When the server is started with --event-scheduler=DISABLED, the value of event_scheduler as displayed in the mysql client is empty, or shown as NULL.

How to repeat:
shell> ./mysqld_safe --event-scheduler=DISABLED &

shell> exit

shell> ./mysql -u root

...

mysql> SHOW VARIABLES LIKE 'event%';
+-----------------+-------+
| Variable_name   | Value |
+-----------------+-------+
| event_scheduler |       | 
+-----------------+-------+
1 row in set (0.00 sec)

mysql> SELECT @@global.event_scheduler;
+--------------------------+
| @@global.event_scheduler |
+--------------------------+
|                     NULL | 
+--------------------------+
1 row in set (0.00 sec)

Suggested fix:
In both cases, the value should be displayed as DISABLED.

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/12466

ChangeSet@1.2317, 2006-09-25 13:49:19+02:00, andrey@example.com +4 -0
  Fix for bug#22662  Inconsistent values displayed for event_scheduler
  when set to DISABLED
  
  It was a silly ordering number error.

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/12484

ChangeSet@1.2320, 2006-09-25 17:22:23+02:00, andrey@example.com +4 -0
  Fix for bug#22662  Inconsistent values displayed for event_scheduler
  when set to DISABLED
    
  It was a silly ordering number error.

pushed to 5.1.12

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented bugfix in 5.1.12 changelog.