You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used to have a very nice connection string against postgresql with "options='--search_path=my_path'" next to the normal user, host, etc. Such that I could use different paths from different areas of my application.
I have an "old" fork in which it works and from a diff I realize that there's been a lot of code committed on November 9th to harmonize code for connection strings between different DBs.
I have been reviewing the code briefly but I didn't find a smoking gun.
This issue is to raise awareness of the lack of backwards compatibility, and of course to talk whether this was just a side-effect and I should solve this differently. (I hope not, because in my last commit for postgresql I spent quite some time assuring this would keep working. - But I'll accept if I'm the only one)
I used to have a very nice connection string against postgresql with "options='--search_path=my_path'" next to the normal user, host, etc. Such that I could use different paths from different areas of my application.
I have an "old" fork in which it works and from a diff I realize that there's been a lot of code committed on November 9th to harmonize code for connection strings between different DBs.
I have been reviewing the code briefly but I didn't find a smoking gun.
This issue is to raise awareness of the lack of backwards compatibility, and of course to talk whether this was just a side-effect and I should solve this differently. (I hope not, because in my last commit for postgresql I spent quite some time assuring this would keep working. - But I'll accept if I'm the only one)