pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed

From: frederikz (@frederikz) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #3722: spring jdbc causes problems with uppercase db names since 42.7.5
Date: Wed, 09 Jul 2025 13:29:12 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Of course, you have to retrieve the results of ``DatabaseMetaData.getColumns`` with upper case column names like ``TABLE_CAT`` but that wasn't the point. The point is that the value returned by the ``TABLE_CAT`` column is case sensitive, So for my database ``abC`` it returns exactly that value ``abC`` and that value has to be used unchanged to call other methods like ``DatabaseMetaData.getColumns``. 
I would understand that ``DatabaseMetaData.storesLowerCaseIdentifiers`` doesn't apply to these metadata methods but then the spring team is using it wrong.
So your understanding of the API is that the return values of ``DatabaseMetaData.getTables`` like catalog have to be used as they are when then querying other metadata methods like ``DatabaseMetaData.getColumns`` and settings like ``DatabaseMetaData.storesLowerCaseIdentifiers`` do not apply to them? It would be nice if you could state something like that, so I could contact the Spring team again. On the postgres side it would then be only somewhat unfortunate that in a minor release we see a change of the value for ``TABLE_CAT`` (previously returning nothing since 42.7.5 returning a value) that causes a problem in other products.

view thread (6+ 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] issue #3722: spring jdbc causes problems with uppercase db names since 42.7.5
  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