Received: from serwer ([213.25.37.66]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f98Bh7n34126 for ; Mon, 8 Oct 2001 07:43:07 -0400 (EDT) (envelope-from jasiek@lamer.pl) Received: from pe78.krakow.cvx.ppp.tpnet.pl ([213.76.40.78] helo=lamer.pl) by serwer with esmtp (Exim 3.12 #1 (Debian)) id 15qCCA-0002bI-00; Sun, 07 Oct 2001 13:34:10 +0200 Message-ID: <3BC165DC.9030D985@lamer.pl> Date: Mon, 08 Oct 2001 10:37:48 +0200 From: Tomasz Myrta X-Mailer: Mozilla 4.78 [en] (Win98; U) X-Accept-Language: pl,en MIME-Version: 1.0 To: Bruce Momjian CC: Tom Lane , Peter Eisentraut , pgsql-sql@postgresql.org Subject: Re: temporary views References: <200110080323.f983NJn04420@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200110/113 X-Sequence-Number: 5068 Bruce Momjian wrote: > > We can handle the temp views thing two ways, either allow views to map > to temp tables by name, or allow temp views to map to temp tables that > exist at creation time and drop the views on session exit. The original > poster clearly wanted the first behavior, but I agree with Peter that > the second has fewer surprises for the user and is more standard. I think, that referring tables by names would be enough. I found another problem connected to this. There is something like this in documetation: "Existing permanent tables with the same name are not visible (in this session) while the temporary table exists." Why not to overlap permanent table? Currently it doesn't work: create table x (a integer); create view y as select * from x; select * from y; OK create temp table x as select * from x; select * from y; ERROR: Relation "x" with OID 364752 no longer exists > I have updated the TODO item to: > > * Allow temporary views Nice to hear it. > It would be interesting of plpgsql could try for an table match by oid > first, and if that fails, try a match by table name and match only if a > temp table is hit. So basically the only table-name matching that would > happen would be hits on temp tables. But why only plpgsql? Would it be difficult to add it to SQL implementation of PostgreSQL? Tomek