java.sql.SQLException: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level (1 reply)

Hello,

MySql Version - 5.5.25

I have a Servoy application which use MySql server as a Database. All of my tables are created using InnoDB engine. It was working without any issues but one day it threw below error message. As per the error I changed the binlog_format to RAW and also MIXED but none of it worked then I decided to change the engine to MyISAM and application works fine again.

Before this error happens the only thing I was trying to do create some indexes.
I tried to create index on a table but I had to kill it because it was struck in the middle. I thought it was due to connections to the DB. Then I restarted the service and created the indexes successfully. This error occur after that incident but it was running without any issues before.


So I decided to remove all the indexes and run the application but never success. It was only success after I changed storage engine to MyISAM.

Could anyone help me to figure out this issue?

java.sql.SQLException: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED. Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.

Thank You