Bug #3876 prepared statements insert are logged incorrectly in update log
Submitted: 24 May 2004 18:37 Modified: 28 May 2004 8:51
Reporter: Sergey Petrunya Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1-bk OS:
Assigned to: CPU Architecture:Any

[24 May 2004 18:37] Sergey Petrunya
Description:
Prepared statements are logged incorrectly in the update log.

How to repeat:
Run mysqld with --log-bin option.
Run tests/client_test.
Look into the update log and see queries like this:
INSERT INTO my_prepare VALUES(?,?,?,?,?,?,?);
[24 May 2004 18:53] Sergey Petrunya
Correction: Start server with --log-update, not --log-bin
[28 May 2004 8:51] Miguel Solorzano
I tested it on Suse 9.1 with the latest 4.1 source tree and I didn't
find the text reported. Instead I found them like the below:

INSERT INTO my_prepare VALUES(92,'MySQL2620',2620,2787,10200,94,7506.281);
# User@Host: root[root] @ localhost []
INSERT INTO my_prepare VALUES(93,'MySQL2645',2645,2797,10300,95,7516.371);
# User@Host: root[root] @ localhost []
INSERT INTO my_prepare VALUES(94,'MySQL2670',2670,2807,10400,96,7526.461);
# User@Host: root[root] @ localhost []
INSERT INTO my_prepare VALUES(95,'MySQL2695',2695,2817,10500,97,7536.551);
# User@Host: root[root] @ localhost []
INSERT INTO my_prepare VALUES(96,'MySQL2720',2720,2827,10600,98,7546.641);
# User@Host: root[root] @ localhost []
INSERT INTO my_prepare VALUES(97,'MySQL2745',2745,2837,10700,99,7556.731);