Skip to content

Fix search_path parameter description and example #4684

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.

Sign up for GitHub

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

Merged
greg-rychlewski merged 1 commit into from
Dec 2, 2025
+2 −2
Merged

Fix search_path parameter description and example #4684

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions guides/howtos/Multi tenancy with query prefixes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ By default, connections to Postgres' databases run on the "public" prefix. When

Luckily Postgres allows us to change the prefix our database connections run on by setting the "schema search path". The best moment to change the search path is during the setup of the database connection, ensuring all of our queries will run on that particular prefix, throughout the connection life-cycle.

To do so, let's change our database configuration in "config/config.exs" and set a `:search_path` parameter in the `:parameters` option. The `:search_path` parameter expects a list of strings that define the search path for the connection:
To do so, let's change our database configuration in "config/config.exs" and set a `:search_path` parameter in the `:parameters` option. The `:search_path` parameter expects a comma separated string of prefixes that define the search path for the connection:

```elixir
config :my_app, MyApp.Repo,
Expand All @@ -93,7 +93,7 @@ config :my_app, MyApp.Repo,
database: "demo_dev",
hostname: "localhost",
pool_size: 10,
parameters: [search_path: ["connection_prefix"]]
parameters: [search_path: "connection_prefix,public"]
```

Now let's try to run the same query as before:
Expand Down
Loading