Bug #16411 Events: Microsecond intervals are allowed
Submitted: 12 Jan 2006 3:59 Modified: 27 Feb 2006 20:20
Reporter: Peter Gulutzan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Stored Routines Severity:S3 (Non-critical)
Version:5.1.6-alpha-debug OS:Linux (linux)
Assigned to: Andrey Hristov CPU Architecture:Any

[12 Jan 2006 3:59] Peter Gulutzan 
Description:
I can say "CREATE EVENT ... EVERY 1 MICROSECOND". But
realistically the switch can't even occur 100 times per second.
So, this is deceptive. Don't allow syntax for what you can't do.

How to repeat:
mysql> create event e_17 on schedule every 1 microsecond do drop table t;
Query OK, 1 row affected (0.00 sec)
[20 Feb 2006 15:08] 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/2917
[24 Feb 2006 13:05] 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/3105
[24 Feb 2006 13:11] 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/3106
[24 Feb 2006 13:12] 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/3107
[24 Feb 2006 14:31] 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/3111
[24 Feb 2006 23:08] Andrey Hristov 
Fixed in 5.1.8. MICROSECOND is disallowed when creating/altering an event. If mysql.event is directly tempered the scheduler will skip the event and refuse to start till the conflicting row is deleted. show create event will give an error in such case. select * from information_schema also.
[27 Feb 2006 20:20] Mike Hillyer 
Documented in 5.1.8 changelog:

      <listitem>
        <para>
          <literal>MICROSECOND</literal> intervals are no longer allowed
          for events. (Bug #16411)
        </para>
      </listitem>