Message-ID: <gh-pgjdbc-pgjdbc-3390-c2539177046@github.com>
From: "SophiahHo (@SophiahHo)" <noreply+SophiahHo@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 12 Dec 2024 14:52:49 +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: SophiahHo
X-GitHub-Comment-Id: 2539177046
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3390
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3390#issuecomment-2539177046
Content-Type: text/plain; charset=utf-8

Changes:
- For DatabaseMetaData methods, the `catalog` argument filters the results by catalog: it must match the current database name or be null to return non-empty results.
- For DatabaseMetaData methods, the returned ResultSet populates the current database name to columns like TABLE_CAT, TABLE_CATALOG, FUNCTION_CAT, PROCEDURE_CAT, PKTABLE_CAT, FKTABLE_CAT, TYPE_CAT.
- For DatabaseMetaData methods, empty strings for the following arguments can filter out results: `schemaPattern`, `tableNamePattern`, `columnNamePattern`, `functionNamePattern`, `procedureNamePattern`, `table`, `schema`, `primaryTable`, `foreignTable`, `primarySchema`, `foreignSchema`, `primaryCatalog`, `foreignCatalog`.