Message-ID: <gh-pgjdbc-pgjdbc-3685-c3004407474@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 25 Jun 2025 11:20:15 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3685: Regression: a query does not work anymore on connection created by `PGSimpleDataSource` but still work with `DriverManager`
In-Reply-To: <gh-pgjdbc-pgjdbc-3685@github.com>
References: <gh-pgjdbc-pgjdbc-3685@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 3004407474
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3685
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3685#issuecomment-3004407474
Content-Type: text/plain; charset=utf-8

> Okay, exploring more the differences between the two URLs, the issue seems to be `?currentSchema=features`. Testing `DriverManager` with the URL built by `PGSimpleDataSource`, it works without `?currentSchema=features` but doesn't work if that fragment is present in the URL.

currentSchema=xyz simply changes the search path upon startup.
> 
> Testing on the command-line with `psql`, the `?currentSchema=features` fragment does not seem to be accepted at all. I do not see that parameter in the page [referenced from here](https://www.prisma.io/dataguide/postgresql/short-guides/connection-uris#specifying-additional-parameters). Is it still supported?

You are conflating psql and pgjdbc. They are not the same
> 
> If not, should `PGSimpleDataSource.setCurrentSchema(String)` be deprecated?
No it should not it is a pgjdbc option