Search for the migrations table in the correct schema #41
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.
Currently, when checking if the
migrations
table has to be created,doesTableExist()
will succeed if there a table namedmigrations
can be found in any schema. This means thatpostgres-migrations
fails to start if there is another table calledmigrations
, even if it's in another schema!In our case, this lead to an incompatibility with graphile-worker, which has its own
migrations
table in its own schema.The fix ensures that only the
public
schema is considered when looking for the table.