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?
Also, Migrations should have a seed method, not the configuration.
Also, Migrations should have a seed method, not the configuration.