MySQL Bugs: #40513: Unable to insert rows to a table when the read

Bug #40513	Unable to insert rows to a table when the read_committed isolation level is used
Submitted:	4 Nov 2008 21:02	Modified:	5 Nov 2008 6:41
Reporter:	John Water	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S2 (Serious)
Version:	5.1.29	OS:	Windows (Win-XP)
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	Isolation level, read committed

Description:
Hi,

It seems there is a bug in the InnoDB storage engine, version 5.1.29RC.  This engine will show the following error:

[MySQL][ODBC 5.1 Driver][mysqld-5.1.29-rc-community]Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'

when an ODBC application (ODBC driver version 5.1.5) with the SQL_TXN_READ_COMMITTED isolation level was trying to insert a row to a table.  This application works well against the MySQL version 5.1.22RC.

Thanks,

John

P.S. a repro will be attacked.

How to repeat:
A repro will be attached.  Here are the steps to repro this problem:

1) Unzip the attached zip file;
2) Issue the following command on Windows
odbcbug "dsn=your_dsn;uid=your_uid;pwd=your_pwd"
Then you'll see this error if the MySQL is 5.1.29.

This one looks like the same as bug#40360. Let Vasil to determine whether it is a duplicate.

This is a duplicate of Bug#40360.

Thanks for reporting!