Is using Entity Framework code first purely for database migrations ok? -
i'm using roundhouse manage database migrations , works nicely.
i have been looking various migration creation technologies fluentmigrator , others. possibility errors though seems high because of them aren't typed. instance migration fluentmigrator
public class createmembertable : migration { public override void up() { create.table("members") .withnamedidcolumn("memberid") .withcolumn("name").asstring().notnullable(); } public override void down() { delete.table("members"); } }
i've used entity framework code-first before , liked migration engine in generates code based migrations can make changes require afterwards. don't need rest of ef framework, it's bit heavyweight i'm looking for.
would acceptable use ef migrations not bother of rest of it? there's nice roundhouse plugin
most of data i'm using flat petapoco or dapper seems lighter solution orm standpoint.
i believe can, have bring mapping pieces of ef. because of i'm not sure how gain on not using ef in code. it's possible, it's tied mapping constructs , context.
one can use rh (roundhouse) refreshdatabase sql files if want go route.
Comments
Post a Comment