Re: Updateable Views? - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: Updateable Views?
Date
Msg-id 4114E622.7070306@Yahoo.com
Whole thread Raw
In response to Re: Updateable Views?  (Greg Stark <gsstark@mit.edu>)
Responses Re: Updateable Views?
List pgsql-hackers
On 8/3/2004 11:38 PM, Greg Stark wrote:

> "Scott Marlowe" <smarlowe@qwest.net> writes:
> 
>> On Tue, 2004-08-03 at 13:05, CSN wrote:
>> > Just wondering, is updateable views slated for a
>> > future version of Postgresql? In addition to using
>> > rules that is.
>> 
>> I would think that a basic fleshing out of the logic with some kind of
>> stored proc to make the views and triggers would likely get someone
>> started on the backend work.  You know, a proof of concept thingy.
> 
> I have some fears here. It seems everyone's first thought when they think
> about updateable views is to think about constructing rules on the views.
> 
> How would that approach help with inline views? Things like:
> 
>  UPDATE (SELECT a+b AS x, c AS y FROM foo) SET c=1 WHERE x = 10

There is no such thing as an "inline view". What you show here is a 
subselect, and I have not heard of "updatable subselects" yet. Could you 
point me to the section in the ANSI SQL specifications that describes 
this feature please?


Jan

> 
> It seems like starting with these types of views in the backend would be more
> productive than implementing something in rules. Once postgres can handle
> inline views it should be trivial to handle persistent views just like they're
> handled on selects.
> 


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PITR - recovery to a particular transaction
Next
From: Oliver Elphick
Date:
Subject: Re: UNICODE characters above 0x10000