You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to validate my migration scripts against an existing database on which I have applied some migration. Now my classpath contains scripts which would be applied on the said database in future.
After 3.0 the validate method defaults the option to allow pendingOrFuture migration in validate method to false.
Whats the purpose of having this configurable item if its defaulted to false?
Can we make it configurable?
Looking at the problem a little deeper I think I agree that the extra config parameter is a bit superfluous. I think I prefer the special value for 'target' to repurposing setIgnoreFailedFutureMigration. The latter I think adds unnecessary ambiguity to that parameter whereas the former would just be formalizing the workaround (and giving access to it from Spring contexts). See PR #913
changed the title
Option to validate against an existing database with pending or future migration not configurable
Option to validate only until current version of the schema
Jan 10, 2015