Message-ID: <gh-pgjdbc-pgjdbc-3722-c3052683252@github.com>
From: "frederikz (@frederikz)" <noreply+frederikz@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 09 Jul 2025 13:29:12 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3722: spring jdbc causes problems with uppercase db names since 42.7.5
In-Reply-To: <gh-pgjdbc-pgjdbc-3722@github.com>
References: <gh-pgjdbc-pgjdbc-3722@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: frederikz
X-GitHub-Comment-Id: 3052683252
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3722
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3722#issuecomment-3052683252
Content-Type: text/plain; charset=utf-8

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.