We are using SqlServer with sqlFiles, and were testing the failure
behavior. We expected a bad insert (string into an int col) to fail the
changeSet and not write the record into the DATABASECHANGELOG table, but
we got different results depending on where the failing insert was
placed in the file. If the failing insert was first, the changeset
failed as expected. If a passing insert was placed before the failing
one, the entire changeset was rolled back (the passing insert was not in
the table) but the changeset was logged as successful in the
DATABASECHANGELOG table.
Has anyone had this happen before? Workarounds? Bug?
Has anyone had this happen before? Workarounds? Bug?