[9.x] Query PostgresBuilder
fixes for renamed config 'search_path'
#41215
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.
Fixes #41213 and more
PostgresBuilder::parseSchemaAndTable()
config('database.connections.pgsql.search_path')
fallback to <= 8.x key'database.connections.pgsql.schema'
.$user
schema variable replacement already done byparseSearchPath()
that this method calls.PostgresBuilder::getAllTables()
+getAllViews()
+parseSchemaAndTable()
config('database.connections.pgsql.search_path')
#41088 fixed valid schemas like 'test-db' not being parsed. These 3 methods still have that problem.parseSearchPath()
was copy & pasted betweenPostgresConnector
andPostgresBuilder
with a one-line difference for $user replacements.ParsesSearchPath
trait to fixPostgresBuilder
methods not handling all search paths.DatabasePostgresBuilderTest
config('database.connections.pgsql.schema')
and cover an array of search paths with non-alphanumeric strings containing hyphen or accented characters.