Message-ID: <gh-pgjdbc-pgjdbc-3390-rc1778589696@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 27 Sep 2024 13:01:19 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
In-Reply-To: <gh-pgjdbc-pgjdbc-3390@github.com>
References: <gh-pgjdbc-pgjdbc-3390@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 1778589696
X-GitHub-Comment-Type: review_comment
X-GitHub-Commit: d3a7a84222e227831e5894b7b64e11e40dbaae8e
X-GitHub-Issue: 3390
X-GitHub-Path: pgjdbc/src/main/java/org/postgresql/jdbc/PgDatabaseMetaData.java
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: review_comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3390#discussion_r1778589696
Content-Type: text/plain; charset=utf-8

(on pgjdbc/src/main/java/org/postgresql/jdbc/PgDatabaseMetaData.java)

as appealing as it is to use the `information schema`, this is actually a view and adds another select into this query. Is there any reason to do this ?