Re: Issue 127 in flyway: Validate should fail if there are migrations in source that have not been run on the database

[fly...@googlecode.com]

Updates:
Summary: Validate should fail if there are migrations in source that have
not been run on the database

Comment #3 on issue 127 by axel.fontaine.business: Validate should fail if
there are migrations in source that have not been run on the database
http://code.google.com/p/flyway/issues/detail?id=127

(No comment was entered for this change.)

[fly...@googlecode.com]

Comment #4 on issue 127 by pardsb...@gmail.com: Validate should fail if

there are migrations in source that have not been run on the database
http://code.google.com/p/flyway/issues/detail?id=127

I would like this feature as well, at least an an optional parameter.

[fly...@googlecode.com]

Comment #5 on issue 127 by sto...@gmail.com: Validate should fail if there

are migrations in source that have not been run on the database
http://code.google.com/p/flyway/issues/detail?id=127

I support this, though I am not sure whether it is sensible to merge this
functionality into the .validate() function - perhaps there should be
a .isUptodate() check. A programmatical check whether the database is
updated is a very nice thing to have. Usecase: for organisatorical reasons
the updates are done separately when the application is down, but the
application should scream if someone forgot to update the database up to
its level.

[fly...@googlecode.com]

Comment #6 on issue 127 by msz...@wp.pl: Validate should fail if there are

migrations in source that have not been run on the database
http://code.google.com/p/flyway/issues/detail?id=127

I also expected validate to do that check, but in fact validate already
does a separate check and I think it should be somehow configurable which
validation should be done (only changes in scripts, not applied migration
or both).
I would like to be able to make a full validation (both mentioned) in an
application's configuration on production environments (to fail fast on
startup), so preferable one method to be able to "call" it from Spring.

[fly...@googlecode.com]

Updates:
Status: Accepted
Labels: Component-Core

Comment #7 on issue 127 by axel.fontai...@gmail.com: Validate

should fail if there are migrations in source that have not been run on the
database
http://code.google.com/p/flyway/issues/detail?id=127

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[fly...@googlecode.com]

Updates:
Status: Migrated

Comment #8 on issue 127 by axel.fontai...@gmail.com: Validate

should fail if there are migrations in source that have not been run on the
database
http://code.google.com/p/flyway/issues/detail?id=127

Migrated to GitHub: https://github.com/flyway/flyway/issues/97

To everyone who starred this issue: please leave a +1 comment on the linked
GitHub issue