We use this to show the list of available databases to the users. I
know, that this list can be retrieved with a select on pg_database, but
our application runs with various database systems and we try to avoid
database specific code. The issues with some of the metadata methods and
Connection.setCatalog don't affect the rest of our code, because the
connections are dedicated to each used database.
Martin Keller
Kris Jurka wrote:
>
>
> On Tue, 29 Nov 2005, Martin Keller wrote:
>
>> newer versions of the PostgreSQL JDBC driver don't return all
>> databases of the server when calling DatabaseMetaData.getCatalogs(...).
>> Can anyone tell me, why this change was neccessary? It's incompatible
>> to JDBC spec and brakes existing code.
>>
>
> This was discussed quite some time ago, starting here:
>
> http://archives.postgresql.org/pgsql-jdbc/2004-01/msg00154.php
>
> The core issue is that while we can return a list of catalogs, you
> can't do anything with them. Connection.setCatalog does nothing.
> Other metadata methods ignore the catalog filter as well. Pretending
> the other catalogs don't exist makes certain applications work better,
> DBVisualizer for example. What are you using it for?
>
> Kris Jurka