Edited Unassigned: Make Migrations DB engine independent. [1364]

As I understand, currently Migrations are dependent on the used Database engine, and don't work, when another engine is used, since the edmx model is checked against a hash of the edmx model used at design time, and the edmx model is not engine independent. Would it be feasible, to check for example for the number of migrations instead of a edmx hash, so the migrations are database independent?
Consider for example a CMS that supports different DB back ends like MySQL or sqlite. At development time one works for example with SQL server and creates all the migrations, but the same migrations should equally work under mysql.