[11.x] Fix dumping migrations table with schema or prefixed name #52098
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.
Alternative to #52076
Dump command uses
hasMigrationTable()
method to determine if themigrations
table exists before dumping its data, this methods callSchema::hasTable()
under the hood which handles the table's prefix and schema name on PostgreSQL.This PR fixes 2 related problems:
hasMigrationTable()
is without prefix, otherwise the table name will get prefixed twice and not be found.Schema::hasTable()
does; Otherwise we are checking if migrations table exists within thesearch_path
and dump it from default schema instead!