Re: POSS. FEATURE REQ: "Dynamic" Views - Mailing list pgsql-general

From Bruce Momjian
Subject Re: POSS. FEATURE REQ: "Dynamic" Views
Date
Msg-id 200508270450.j7R4oix28325@candle.pha.pa.us
Whole thread Raw
In response to Re: POSS. FEATURE REQ: "Dynamic" Views  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: POSS. FEATURE REQ: "Dynamic" Views  ("Jim C. Nasby" <jnasby@pervasive.com>)
Re: POSS. FEATURE REQ: "Dynamic" Views  (Greg Stark <gsstark@mit.edu>)
List pgsql-general
Jim C. Nasby wrote:
> > I wonder whether it would be saleable to have an option to work around this
> > "feature". I'm thinking one of two directions:
> >
> > 1) An alternate type of view that just stores the text of the view and is
> > interpreted at time of use like:
> >
> > CREATE DYNAMIC VIEW foo AS (SELECT * FROM tab)
> >
> > or 2) A command to recompile a view which would go back to the original source
> > and reinterpret it like:
> >
> > ALTER VIEW foo RECOMPILE
> >
> > Or I guess you could have the latter and then add the former as a view that
> > automatically recompiles any time a object it depends on is altered.
>
> I agree that CREATE DYNAMIC would be a good thing to have. It would
> certainly save me time on some of my projects.
>
> Can we TODO this?

How is this different from materialized views, which is already on the
TODO list?

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-general by date:

Previous
From: Chris Travers
Date:
Subject: Re: Postgresql replication
Next
From: Greg Stark
Date:
Subject: Re: About "ERROR: must be *superuser* to COPY to or from a file"