-
Notifications
You must be signed in to change notification settings - Fork 891
Allow changing db schema from public #4873
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
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
recheck |
1 similar comment
recheck |
Hey @mafredri! Could you please take a look at this draft PR to check if I don't miss anything? |
There seems to be one more case of
But other than that, looks great! If you want to take a stab at documenting how to use this feature, there's an issue (that got closed by stale bot) to improve the documentation for setting up PostgreSQL: #3508 |
Good catch, @mafredri!
Absolutely, I can take a look at it later and document that part. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, looks good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
Fixes: #4747
This PR removes hard-coded references to the
public
schema, which prevents users from predefining their own schemas. As the application depends on the connection string, I suppose that it doesn't need an extra ENV var (likeDB_SEARCH_STRING
in https://github.com/coder/v1/pull/13216) to provide thesearch_path
.