Message-ID: <gh-pgjdbc-pgjdbc-3568-c2772381643@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 02 Apr 2025 12:17:43 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3568: use pgType instead of internal name to preserve the schema
In-Reply-To: <gh-pgjdbc-pgjdbc-3568@github.com>
References: <gh-pgjdbc-pgjdbc-3568@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 2772381643
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3568
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3568#issuecomment-2772381643
Content-Type: text/plain; charset=utf-8

So the problem with this is that we presume that the current schema would be 'public'. Now we can add code to check for the current schema but then when we change the schema we would have to invalidate the cache. 
That might not be the worst thing in the world.
Thoughts ? @vlsi @sehrope ?