Re: Bug with DatabaseMetaData and temporary tables/schemas - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: Bug with DatabaseMetaData and temporary tables/schemas
Date
Msg-id alpine.BSO.2.00.1012221159040.9197@leary.csoft.net
Whole thread Raw
In response to Re: Bug with DatabaseMetaData and temporary tables/schemas  (Thomas Kellerer <spam_eater@gmx.net>)
Responses Re: Bug with DatabaseMetaData and temporary tables/schemas
List pgsql-jdbc

On Sun, 7 Nov 2010, Thomas Kellerer wrote:

> Tom Lane wrote on 07.11.2010 02:02:
>> Kris Jurka<books@ejurka.com>  writes:
>>> It looks like psql will show you your own temp schema and all of the
>>> temp toast schemas.  So that could potentially be improved as well.
>>
>> Yeah, there was some discussion of that just recently:
>> http://archives.postgresql.org/message-id/16710.1284837096@sss.pgh.pa.us
>>
>> I haven't got round to making that change yet, but maybe now is a
>> good time.  The consensus seemed to be that \dn (without S) should
>> not show any pg_XXX schemas, nor information_schema.  Not sure that
>> that's appropriate for getSchemas though --- an API intended for
>> programs should maybe just hide the temp and toast schemas.
>>
>
> Well it should at least show "my" temp schemas.

I've applied a patch to fix this.  The driver will now show your own temp
schema and toast temp schema, but no other temp schemas (toast or
otherwise).

> Or getColumns() and getTables() should be smart enough to return information
> about temp tables without having to specify the temp schema.

I'm not sure what you are referring to here.  You can certainly leave the
schema blank and it should work.

Kris Jurka

pgsql-jdbc by date:

Previous
From: Richard Broersma
Date:
Subject: Re: Comparing Enumerated Types between JDBC and ODBC drivers
Next
From: Thomas Kellerer
Date:
Subject: Re: Bug with DatabaseMetaData and temporary tables/schemas