8000 Add PostgreSQL Changes to Upgrade Guide by cbj4074 · Pull Request #6657 · laravel/docs · GitHub
[go: up one dir, main page]

Skip to content

Add PostgreSQL Changes to Upgrade Guide #6657

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,6 +127,17 @@ Next, in your `composer.json` file, remove `classmap` block from the `autoload`
}
},

<a name="postgres-configuration"></a>
#### PostgreSQL Configuration Changes

**Likelihood Of Impact: Low**

In previous Laravel versions, the term "schema" (a single schema) was used when "search path" (a list of schemas) was intended. Accordingly, variable names, comments, and configuration directives were updated to correct the terminology and intent.

This change will not affect most users, however, the `schema` configuration key on PostgreSQL database connections has been renamed to `search_path`, so if you are not using the default `pgsql` connection, exclusively, you will need to update your database configuration(s) accordingly.

Finally, you may now specify a `search_path` that contains more than one schema in your `.env` file using a comma-separated string, e.g., `DB_SEARCH_PATH='"$user", "laravel"'`. (In previous Laravel versions, this was possible only by adding parsing logic to the array in your configuration file.)

<a name="eloquent"></a>
### Eloquent

Expand Down
0