Re: AW: [HACKERS] Another TEMP table trick

From: Hannu Krosing <hannu(at)trust(dot)ee>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: Zeugswetter Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at>, hackers(at)postgreSQL(dot)org
Subject: Re: AW: [HACKERS] Another TEMP table trick
Date: 1999-01-30 11:44:17
Message-ID: 36B2F091.7EC6EDB1@trust.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
>
> > There could be a problem with GUI tools that rely on these rows
> > to format their output (like pgaccess or ODBC --> M$ Access) though.
>
> Oh, never thought of that. A select of pg_class will return no rows for
> that table because it is a temp table.

One more reson to move \d from psql to backend maybe with syntax like
Oracle's "DESC xxx" unless there is something in ANSI standard for that.

Or implement the ANSI system tables (I think there were some ;) and
views.

Then the front-end tools can be advised to use these (and TEMP TABLES
can
add rows to other (possibly structure-permanent) TEMP tables that are
UNIONed
withe real pg_class to give them real values.

Or we can even implement just temp _rows_ for tables that exist in a
session only (maybe like in independant uncommitted transactions),
and add the info for temp tables to pg_class (and friends) as temp rows.

----------------
Hannu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 1999-01-30 11:47:52 Re: [HACKERS] READ COMMITTED isolevel is implemented ...
Previous Message Vadim Mikheev 1999-01-30 11:09:06 Re: [HACKERS] READ COMMITTED isolevel is implemented ...