validateOnMigrate is true by default

[vertex-github]

We just had a case where additional SQL was added to an already applied SQL change file. On databases that already had the SQL change file applied, Flyway ignored the new additions since as far as it was concerned, the changeset had been applied. However, this led to problems since developers working off fresh DB copies got the new changeset (as did all unit tests that leverage in-memory DBs like H2), pushed changes to prod, and ended up with an inconsistent DB.

Could Flyway also check that the provided SQL files had not been modified since they were applied, and if so report an error (fail fast, rather than ignore the changeset) if this is the case?

[axelfontaine]

Set validateOnMigrate to true and you should be good to go.

I'll look into improving the documentation for this on the website.

[vertex-github]

Awesome! Many thanks.

In the spirit of fail-fast, is there a reason that this property isnt set by default?

Nick

On Tue, Feb 11, 2014 at 11:40 AM, Axel Fontaine notifications@github.comwrote:

Set validateOnMigrate to true and you should be good to go.

I'll look into improving the documentation for this on the website.

Reply to this email directly or view it on GitHubhttps://github.com//issues/695#issuecomment-34773078
.

[axelfontaine]

As of Flyway 3.0, validateOnMigrate is now true by default.

[mohitsins]

where to set the property false please explain