I created a test migration which creates a table and then forces an
error. The error causes the runner to crash and then the database is
left with the table still there, but no row is added to the
VersionInfo table. This is leaving the database in a broken state. Is
there a plan to wrap migrations in a transaction, or should this be
handled some other way?
--
You received this message because you are subscribed to the Google Groups "FluentMigrator Google Group" group.
To post to this group, send email to fluentmigrato...@googlegroups.com.
To unsubscribe from this group, send email to fluentmigrator-goog...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fluentmigrator-google-group?hl=en.
I can see what it would take to implement, or if you want to submit a
patch I can apply.
Thanks
Sean
> > fluentmigrator-goog...@googlegroups.com<fluentmigrator-goo gle-group%2Bunsu...@googlegroups.com>
If anyone wants to test it out and make sure it looks good. All tests
are passing and I added an integration test to confirm that it's
working as expected.
http://github.com/enkari/fluentmigrator/commit/e776961219bbc5bdb6693832b1bc724384759e8e
To unsubscribe from this group, send email to fluentmigrator-goog...@googlegroups.com.
Sean thanks this is great. Its been something I have wanted for a while as well.
On Jan 25, 2010 9:30 PM, "Sean Chambers" <scham...@gmail.com> wrote:
I've added the start of transaction support. So far only Sql Server is
supported.
If anyone wants to test it out and make sure it looks good. All tests
are passing and I added an integration test to confirm that it's
working as expected.
http://github.com/enkari/fluentmigrator/commit/e776961219bbc5bdb6693832b1bc724384759e8e
On Jan 25, 10:18 pm, Sean Chambers <schamber...@gmail.com> wrote: > good point, something i've run ...