Re: Allowing COPY into views - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Allowing COPY into views
Date
Msg-id 20070419155942.GA13817@alvh.no-ip.org
Whole thread Raw
In response to Re: Allowing COPY into views  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Allowing COPY into views
List pgsql-hackers
Gregory Stark wrote:
> "Karl O. Pinc" <kop@meme.com> writes:
> 
> > Rather than spend a whole lot of time figuring
> > out all the calls to use and all the detail,
> > I'm going to go ahead and post now.  That way
> > if this is simply not going to fly I don't have
> > to spend any more time on it.  Otherwise,
> > I'll post more as I work it out.
> 
> It probably doesn't make sense to work on just this one case. There are folks
> looking at update-able views. If we had that then this would simplify to
> simply recognizing the case and invoking the rewriter to get you the insert
> statement to use.

The threads to updatable views have concluded rejecting the patches, and
with ideas that require rather extensive rewriting of the rule manager,
so I'd think that handling this one case (COPY view FROM foo) would be
useful on its own, and would carry a lot less work than the whole thing.

Updatable views are not going to handle COPY anyway ...

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Martin Langhoff
Date:
Subject: Re: Hacking on PostgreSQL via GIT
Next
From: KaiGai Kohei
Date:
Subject: Re: [RFC] PostgreSQL Access Control Extension (PGACE)