Message-ID: <gh-pgjdbc-pgjdbc-538-c1346570989@github.com>
From: "lukaseder (@lukaseder)" <noreply+lukaseder@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 12 Dec 2022 14:07:34 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #538: Why getSchemaName return empty string or exists getBaseSchemaName and getColumnName return getColumnLabel?
In-Reply-To: <gh-pgjdbc-pgjdbc-538@github.com>
References: <gh-pgjdbc-pgjdbc-538@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: lukaseder
X-GitHub-Comment-Id: 1346570989
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 538
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/538#issuecomment-1346570989
Content-Type: text/plain; charset=utf-8

> Well it can but most people don't really wan't to take the hit of doing another round trip

But the result is cached in `BaseConnection::getFieldMetadataCache`, so between the various calls to `PgResultSetMetaData`, the extra round trip is shared as good as possible. Given that a round trip is highly likely already, I think that most people will not mind?

> My admittedly fuzzy recollection here is that folks expected the schema name to be returned by the server in the results.

That would be much better, no doubt. But apparently, this information isn't already present now.

Anyway, I just wanted to add this information here, given that I had to look it up myself and that I haven't seen anyone else mention the existing cached data from other round trips.