Hello,

I am working on an application working with a version 5 of mySQL. In
our mySQL server, binary logging is enabled as replication of the base
is activated.

But I noticed that when my app tries to insert data (with INSERT INTO
statement) on the database, insert is not made and I get an error
message (Binary Logging not Possible. Message: Transaction Level
READ-COMMITTED in InnoDB is not Safe for Binlog Mode STATEMENT).

I have been looking on the Internet about this message, but I'd like to
know if somebody have experience about this problem, and if a
workaround exist to allow the insertions and also to allow binary
logging at the same time.

Thank you.

Yo a formulé la demande :

FYI, it seems that setting binary logging mode to RAW instead of
STATEMENT (default value) solve this issue. :-)

Yo <nomail (AT) nomail_invalid (DOT) net> wrote:

[Transaction Level READ-COMMITTED in InnoDB is not Safe
for Binlog Mode STATEMENT]

ITYM binlog mode is ROW now. And yes, this will work, just
like binlog mode MIXED.

See: http://dev.mysql.com/doc/refman/5.1/...g-formats.html

But the much better way out would have been to not use the
READ-COMMITTED transaction isolation level but to stay with
the default REPEATABLE-READ. Or do you have a good reason
for using READ-COMMITTED?

See: http://dev.mysql.com/doc/refman/5.1/...ansaction.html


XL