From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Bug with DatabaseMetaData and temporary tables/schemas |
Date: | 2010-11-07 08:43:33 |
Message-ID: | ib5ork$45l$1@dough.gmane.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Tom Lane wrote on 07.11.2010 02:02:
> Kris Jurka<books(at)ejurka(dot)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.
Or getColumns() and getTables() should be smart enough to return information about temp tables without having to specify the temp schema.
Regards
Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fork | 2010-11-08 13:54:30 | PSQLException: The column name <col> was not found in this ResultSet. |
Previous Message | Tom Lane | 2010-11-07 01:02:41 | Re: Bug with DatabaseMetaData and temporary tables/schemas |