Message-ID: <gh-pgjdbc-pgjdbc-3606-c2823869415@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 23 Apr 2025 10:43:57 +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: 2823869415
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-2823869415
Content-Type: text/plain; charset=utf-8

@cgm-aw I wish it were that easy.
Past experience has demonstrated that people use the drivers in ways I hadn't imagined.
I'm fine with changing the set/getSchema to handle multiple schemas; but get needs to return what was passed in set. 
We would just have to push this off to a major release. I think we are close to a minor release, and we can fast follow with a major release