Click here to Skip to main content
15,887,135 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
Given the significant cost and availability difference between MySQL and MSSQL with local hosting providers, I am looking to convert some simpler projects to use MySQL. I'm wondering if this will be a very uncomfortable experience, or simply a matter of getting used to some differences w.r.t. EF, not in the DBs themselves.

I recently grew very frustrated that EF kept generating migrations that would fail on SqlCe, and require painful manual edits, e.g. SqlCe will not allow a column rename, so migrations must be updated to drop and recreate columns, a far more 'invasive' process.

If you have used MySql with EF, do you have any warnings or advice for me?
Posted
Comments
phil.o 24-Oct-15 3:22am    
I don't have done any significant project with EF/MySQL, but what I know is that working with SQL CE becomes a bigger mess at each VS version.
MySQL does not suffer from this problem, and the ADO.NET library is well maintained; so it could be worth the try.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900