Message-ID: <gh-pgjdbc-pgjdbc-3606-c2812981222@github.com>
From: "cgm-aw (@cgm-aw)" <noreply+cgm-aw@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 17 Apr 2025 13:43:40 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3606: fix: add support for multiple schemas via PgConnection.setSchema
In-Reply-To: <gh-pgjdbc-pgjdbc-3606@github.com>
References: <gh-pgjdbc-pgjdbc-3606@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: cgm-aw
X-GitHub-Comment-Id: 2812981222
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3606
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3606#issuecomment-2812981222
Content-Type: text/plain; charset=utf-8

> FYI If one of the list items is the special name $user, then the schema having the name returned by CURRENT_USER is substituted, if there is such a schema and the user has USAGE permission for it. (If not, $user is ignored.)

Ah thanks, I didn't know that.
I guess there are points to both sides - a `get` should return the state that a `set` established, but also the new `getSchema` implementation might break code for people who didn't even know they had multiple schemas on their search path. Adding the new behavior to the changelog should be enough to clarify this, though.
The [Javadoc](https://docs.oracle.com/en/java/javase/17/docs/api/java.sql/java/sql/Connection.html#getSchema()) doesn't have much to say on this. 
Changing `getSchema` is obviously trivial, so let me know which behavior you want.