Would dapper have any problems with using two IDbConnection objects for distributing Writes and Reads between MySQL Master/Slaves?
Would dapper have any problems with using two IDbConnection objects for distributing Writes and
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Would dapper have any problems with using two IDbConnection objects for distributing Writes and Reads between MySQL Master/Slaves?
No, not at all.
Dapper’s identity cache uses the connection string as part of the key. This means you could even have your tables “out-of-column-order” in both the master and slave, and dapper would cope fine with it.