Skip site navigation (1) Skip section navigation (2)

AW: AW: Backend-internal SPI operations

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "'Jan Wieck'" <janwieck(at)Yahoo(dot)com>, Mark Hollomon <mhh(at)nortelnetworks(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: AW: AW: Backend-internal SPI operations
Date: 2000-08-31 15:00:59
Message-ID: 11C1E6749A55D411A9670001FA687963368063@sdexcsrv1.f000.d0188.sd.spardat.at (view raw or flat)
Thread:
Lists: pgsql-hackers
> Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> writes:
> > I don't see why a real view should still be createable by the old
> > create table then create rule way.
> 
> Because we'll need to be able to read dump files created by existing
> versions of pg_dump.  If we don't cope with CREATE TABLE + CREATE RULE
> then restored-from-dump views won't really be views and will act
> differently from freshly created views.  Avoiding the resulting
> support headaches is worth a little bit of ugliness in the code.

Well, since an on select do instead rule on a whole table is offhand 
only good for a view I do agree. (At least I can't think of another use)
 
The only worry I have is that it should not destroy the possibility for real

on select do instead rules on single attributes.

Andreas

Responses

pgsql-hackers by date

Next:From: Jan WieckDate: 2000-08-31 15:07:57
Subject: Re: More about "CREATE TABLE" from inside a function/trigger...
Previous:From: Ross J. ReedstromDate: 2000-08-31 14:53:04
Subject: Re: AW: Backend-internal SPI operations

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group