As discussed in #43 and #85 there are problems when the database contains migrations which are not part of the current plan. Up to this PR sql-migrate was just ignoring such cases and hoped for the best.
The PR adds a new error type PlanError and uses it when a mismatch between the database migrations and the current source migrations is found. This way one would be able to ignore this error while using sql-migrate as a library if need be.
As discussed in #43 and #85 there are problems when the database contains migrations which are not part of the current plan. Up to this PR
sql-migrate
was just ignoring such cases and hoped for the best.The PR adds a new error type
PlanError
and uses it when a mismatch between the database migrations and the current source migrations is found. This way one would be able to ignore this error while usingsql-migrate
as a library if need be.