.net - FluentMigrator Failed Migrations Don't Rollback? -


I started experimenting with bus I saw that the failed migration was not being brought back to what it still applies Has not happened? It feels very bad because it leaves the database in broken condition.

For example, the migration from below will obviously fail when it tries to add Table1 the second time (I'm doing this just to apply an error). I hope the migration should be included in a transaction, which will start when it fails. [Migration (1)] Public class AddTable: Migration {Public Override Zero (up)} Create.Table ("Table1") WithIdColumn () .; Create.Table ("Table1") WithIdColumn () .; } Public Override Down () {Delete Tables ("Table 1"); }}

However, what happens instead is that the runner throws an error (which causes the console app to crash) and the database is left with Table 1 and the version There is no line in the difference table, it seems like a bad situation to leave things.

Using the latest FluentMagger code (as of today), is running with Visual Studio 2008 and SQL Server 2008 Express.

Support for transactions on January 26th.


Comments

Popular posts from this blog

oracle - The fastest way to check if some records in a database table? -

php - multilevel menu with multilevel array -

jQuery UI: Datepicker month format -