pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: sehrope (@sehrope) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] PR #3568: use pgType instead of internal name to preserve the schema
Date: Wed, 02 Apr 2025 12:40:21 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
I think you left out the SQL part of that comment :D
The more we think about these metadata functions, the more weird and annoying edge cases we're going to find. The only consistent answers I can think of are:
* Always query everything at point of use
* Always cache / infer everything using initial search path etc
The first one sucks as it's likely unneeded 99.99% of the time. The second one will be wrong for any changes to search path etc (but at least it's consistently wrong...). Maybe anybody that does that stuff should really be querying the catalogs in their application code as they're already doing non-JDBC specific actions right?
view thread (11+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] PR #3568: use pgType instead of internal name to preserve the schema
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox