You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the BeginTransaction method in TransformationProvider always uses IsolationLevel.ReadCommitted to begin the transaction. In MySQL 5.1.66 if you are using InnoDB tables and Statement based replication the isolation level must be either IsolationLevel.RepeatableRead or IsolationLevel.Serializable.
Could the TransformationProvider be updated so that the isolation level was configurable via a property? Or as a argument to the BeginTransaction method?
The text was updated successfully, but these errors were encountered:
eliog
pushed a commit
to eliog/Migrator.NET
that referenced
this issue
Sep 16, 2019
Currently the BeginTransaction method in TransformationProvider always uses IsolationLevel.ReadCommitted to begin the transaction. In MySQL 5.1.66 if you are using InnoDB tables and Statement based replication the isolation level must be either IsolationLevel.RepeatableRead or IsolationLevel.Serializable.
Could the TransformationProvider be updated so that the isolation level was configurable via a property? Or as a argument to the BeginTransaction method?
The text was updated successfully, but these errors were encountered: