From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, iharding(at)destinydata(dot)com, CSN <cool_screen_name90001(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: POSS. FEATURE REQ: "Dynamic" Views |
Date: | 2005-08-27 04:50:44 |
Message-ID: | 200508270450.j7R4oix28325@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2005-08-27 05:20:29 | Re: About "ERROR: must be *superuser* to COPY to or from a file" |
Previous Message | Chris Travers | 2005-08-27 01:26:22 | Re: Postgresql replication |