Bug #23483 Wrong definition of Event naming behaviour
Submitted: 19 Oct 2006 23:17 Modified: 10 Dec 2006 5:18
Reporter: Peter Volk (Basic Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.1 OS:Any (All)
Assigned to: Jon Stephens CPU Architecture:Any
Tags: documentation, events

[19 Oct 2006 23:17] Peter Volk 
Description:
The documentation (http://dev.mysql.com/doc/refman/5.1/en/events-limitations-restrictions.html) describes in the last section that the event names are cas insensitive. and are distinct by database and definer
<cite>cannot have two events in the same database and with the same definer </cite>

This behavior has been changed since 5.1.6 to the point that the events are database specific only.  

How to repeat:
None

Suggested fix:
change the citation above to:

<cite>cannot have two events in the same database</cite>
[20 Oct 2006 7:12] Sveta Smirnova 
Thank you for the report.

Verified as described on Linux using last BK sources.
[10 Dec 2006 5:18] Jon Stephens 
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

NOTE: Actually, events were differentiated according to definer through MySQL 5.1.11, not 5.1.6 (see http://dev.mysql.com/doc/refman/5.1/en/events-overview.html). Therefore, I've altered the first sentence of the paragraph in question to read:

  Beginning with MySQL 5.1.8, event names are handled in case-insensitive 
  fashion. For example, this means that you cannot have two events in the same   
  database (and - prior to MySQL 5.1.12 - with the same definer) with the names 
  anEvent and AnEvent.