Changing isolation level for data context
Posted: Tue 26 May 2015 07:42
Hello,
We use dotConnect for Mysql. We also need to use replication and we want to keep STATEMENT binlog mode.
Is it possible to change default transaction isolation level for insert/update queries through data context? We set REPEATABLE READ as default for Mysql server. However, "SubmitChanges()" method still override this setting by executing statement to change it to "READ COMMITED".
Then we get exception:
"Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'"
I know that there is a workaround to wrap all queries to explicit transaction. However, it is really not possible for complex projects. We can't change thousands rows of a code. Is it anyhow possible to avoid changing isolation level in SubmitChanges method?
Thank you.
We use dotConnect for Mysql. We also need to use replication and we want to keep STATEMENT binlog mode.
Is it possible to change default transaction isolation level for insert/update queries through data context? We set REPEATABLE READ as default for Mysql server. However, "SubmitChanges()" method still override this setting by executing statement to change it to "READ COMMITED".
Then we get exception:
"Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'"
I know that there is a workaround to wrap all queries to explicit transaction. However, it is really not possible for complex projects. We can't change thousands rows of a code. Is it anyhow possible to avoid changing isolation level in SubmitChanges method?
Thank you.