MySQL Bugs: #16404: Events: keyword is ENABLED rather than ENABLE

Bug #16404	Events: keyword is ENABLED rather than ENABLE
Submitted:	12 Jan 2006 3:48	Modified:	2 Feb 2006 4:45
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 (SUSE 10.0)
Assigned to:	Andrey Hristov	CPU Architecture:	Any

Description:
I can say "CREATE EVENT ... [DISABLED|ENABLED] ..." but
it would be better if I could instead say
"CREATE EVENT ... [DISABLE|ENABLE]", for both
CREATE and ALTER.

How to repeat:
mysql> create event if not exists e_12 on schedule every 1 second disabled do drop table t;
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> create event if not exists e_12 on schedule every 1 second disable do drop table t;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'disable do drop table t' at line 1

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

Fixed in 5.1.6

It was decided to be compatible with Sybase to use ENABLE and DISABLE instead of ENABLED and DISABLED as keywords in CREATE/ALTER EVENT

Documented in 5.1.6 changelog:

 <listitem>
        <para>
          <emphasis role="bold">Incompatible change</emphasis>:
          <literal>DISABLED</literal>/<literal>ENABLED</literal>
          keywords in <literal>CREATE EVENT</literal> and <literal>ALTER
            EVENT</literal> changed to
          <literal>DISABLE</literal>/<literal>ENABLE</literal>. (Bug
          #16404)
        </para>
      </listitem>