Author: jstephens
Date: 2006-03-09 13:23:49 +0100 (Thu, 09 Mar 2006)
New Revision: 1539
Log:
Precision of event timings - ref Bug #16522. (Thanks, Andrey and PeterG!)
Modified:
trunk/refman-5.1/events.xml
Modified: trunk/refman-5.1/events.xml
===================================================================
--- trunk/refman-5.1/events.xml 2006-03-09 02:53:06 UTC (rev 1538)
+++ trunk/refman-5.1/events.xml 2006-03-09 12:23:49 UTC (rev 1539)
@@ -1314,7 +1314,16 @@
<para>
The resolution of event schedules is measured in seconds. There is
no way to cause events scheduled to occur at the same second to
- execute in a given order.
+ execute in a given order. In addition, due to rounding, the nature of
+ threaded applications, and the fact that a non-zero length of time
+ is required to create events and to signal their execution, events
+ may be delayed by as much as 1 or 2 seconds. However, the time
+ shown in the <literal>INFORMATION_SCHEMA.EVENTS</literal> table's
+ <literal>LAST_EXECUTED</literal> column or the
+ <literal>mysql.event</literal> table's
+ <literal>last_executed</literal> column is always accurate to
+ within one second of the time the event was actually executed.
+ (See also Bug #16522.)
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1539 - trunk/refman-5.1 | jon | 9 Mar |