Fix previous_version: Take inferred migrations into account #631
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add
includeInferred
parameter to functionprevious_version
.If it's
false
, it will behave exactly as it did before this PR. It will be called withfalse
inComplete
, to ignore inferred migrations when dropping the version schema, because inferred migrations do not have version schemas.If it's
true
,inferred
migrations will be taken into account when finding the previous version. It will be called withtrue
when finding the previous version forRollback
.When inferred migrations were not taken into account,
Rollback
was causing a segmentation violation because of nil pointer for new columns/tables added by SQL.This PR also modifies the test
TestNoVersionSchemaForRawSQLMigrationsOptionIsRespected
so that we will be testingPreviousVersion
with both options.Fixes: #623