Message-ID: <gh-pgjdbc-pgjdbc-3606-c3718457232@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 07 Jan 2026 11:31:28 +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: davecramer
X-GitHub-Comment-Id: 3718457232
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-3718457232
Content-Type: text/plain; charset=utf-8

@cgm-aw It looks like the setSchema tests are failing.
I've thought about this PR a bit more. 
What do you think of keeping the behaviour the way it is now unless the user calls setSchema with multiple schema's. At that point we return multiple schema's but not before.

That way we keep the current behaviour unless the client specifically asks for it.
@vlsi ?

Thoughts ?