[3.x] Update PostgreSQLSchemaManager to set correct config key value #840
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.
In Laravel 9.0, the Postgres
schema
config key has been replaced bysearch_path
(https://laravel.com/docs/9.x/upgrade#postgres-schema-configuration).This PR updates the
PostgreSQLSchemaManager
to check which config value is in use and sets it accordingly. It might be worth setting both no matter whether the key exists or not, but I thought this would be the best solution.