| Bug #20346 | MySQL starts with event_scheduler=2 although my.ini sets it to 1 | ||
|---|---|---|---|
| Submitted: | 8 Jun 2006 18:48 | Modified: | 10 Jun 2006 11:45 | 
| Reporter: | Markus Popp | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) | 
| Version: | 5.1.11 | OS: | Windows (Windows) | 
| Assigned to: | Sveta Smirnova | CPU Architecture: | Any | 
   [8 Jun 2006 18:48]
   Markus Popp        
  
 
   [8 Jun 2006 18:49]
   Markus Popp        
  Additional note: after killing the process from another client, event-scheduler was set to 1.
   [8 Jun 2006 18:54]
   Markus Popp        
  Maybe this is a bug on its own, but this doesn't work after having the event_scheduler value set to 1:
DROP TABLE tt;
CREATE TABLE  `tt` (
   `id` int(10) unsigned NOT NULL auto_increment,
   `d` int(10) unsigned NOT NULL,
   `ts` timestamp NOT NULL,
   PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
DELIMITER //
DROP EVENT insertIntoTT //
CREATE EVENT insertIntoTT
ON SCHEDULE EVERY 5 SECOND
STARTS current_timestamp + INTERVAL 5 SECOND
DO
BEGIN
  insert into tt (d) values (floor(rand() * 100));
END //
DELIMITER ;
Here's the output:
mysql> select * from tt;
Empty set (0.00 sec)
mysql> show events\G
*************************** 1. row ***************************
            Db: test
          Name: insertIntoTT
       Definer: mpopp@localhost
          Type: RECURRING
    Execute at: NULL
Interval value: 5
Interval field: SECOND
        Starts: 2006-06-08 18:51:06
          Ends: NULL
        Status: ENABLED
1 row in set (0.02 sec)
mysql> select * from tt;
Empty set (0.00 sec)
mysql> select @@event_scheduler;
+-------------------+
| @@event_scheduler |
+-------------------+
|                 1 |
+-------------------+
1 row in set (0.00 sec)
 
   [8 Jun 2006 19:13]
   Andrey Hristov        
  As said, it does not have problems on Linux
   [10 Jun 2006 11:45]
   Sveta Smirnova        
  Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to 'Open'. Thank you for your interest in MySQL. Additional info: On my Windows XP SP2 it does not have problems too.
