Bug #16413 Events: statements don't appear in the general query log
Submitted: 12 Jan 2006 4:02 Modified: 3 Mar 2006 6:41
Reporter: Peter Gulutzan Email Updates:
Status: Closed Impact on me:
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

[12 Jan 2006 4:02] Peter Gulutzan
If there is a general log, it should record all statements
such as successful INSERTs. But it doesn't. If the INSERT
happens due to an event, no general-message entry is

How to repeat:

Assume there is a database named db1.

Start mysqld with
mysqld --user=root --skip-networking --log=/tmp/general.txt

On client say:

mysql> use db1;
Database changed

mysql> create table t_19 (s1 int);
Query OK, 0 rows affected (0.01 sec)

mysql> create event e_19 on schedule every 1 second do insert into db1.t_19 values (1);
Query OK, 1 row affected (0.00 sec)

mysql> set global event_scheduler = 1;
Query OK, 0 rows affected (0.00 sec)

Wait several seconds.
Make sure the INSERTs are happening, by selecting from t_19
or by looking at the "RetCode=0" messages on mysqld.
Shut down client and server.
Look at /tmp/general.txt. It has no INSERT statements.
[1 Mar 2006 15:30] 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:

[2 Mar 2006 22:08] Andrey Hristov
Fixed in 5.1.8
[3 Mar 2006 6:41] Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Documented fix in 5.1.8 changelog. Closed.