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

Re: Why does an ON SELECT rule have to be named "_RETURN"?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, ken(at)sunward(dot)org
Subject: Re: Why does an ON SELECT rule have to be named "_RETURN"?
Date: 2006-02-16 16:35:33
Message-ID: 28940.1140107733@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> This is semi-orthogonal, but I'd hoped that with first-class updatable
> views we might get some method to determine which columns are actually
> updatable, but perhaps this is just wishful thinking? 

All of them I should think.  I certainly don't see us automatically
creating update rules for any cases where this isn't so.

			regards, tom lane

In response to

pgsql-general by date

Next:From: Scott MarloweDate: 2006-02-16 16:41:05
Subject: Re: Oracle tried to buy MySQL
Previous:From: Scott MarloweDate: 2006-02-16 16:33:43
Subject: Re: Oracle purchases Sleepycat - is this the "other shoe"

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