-
-
Notifications
You must be signed in to change notification settings - Fork 518
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
fix: update setting search path in postgres #2241
fix: update setting search path in postgres #2241
Conversation
When using multiple schemas in search path for postgres, using quoted string breaks the ability to use multiple schemas. Removing the quotes fixes it.
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.
Thanks!! @jdrouet for spotting this.
Related discussions: https://dba.stackexchange.com/a/175116
I adding a test case to validate it's actually working as expected :)
Hey @tyt2y3, ready for review! |
👋 gentle bump |
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.
Thank you
🎉 Released In 1.0.0-rc.6 🎉Thank you everyone for the contribution! |
🎉 Released In 1.0.0 🎉Thank you everyone for the contribution! |
Bug Fixes
When doing
ops.set_schema_search_path("first_schema,public")
, the initial code only took into consideration thefirst_schema
because of the quotes in'{schema}'
. Removing the quotes fixes this.