Re: POSS. FEATURE REQ: "Dynamic" Views

From: Ian Harding <harding(dot)ian(at)gmail(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: CSN <cool_screen_name90001(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: POSS. FEATURE REQ: "Dynamic" Views
Date: 2005-08-26 04:12:05
Message-ID: 72560230050825211260dada5a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Brand X simulates this in their GUI diagrammer by tracking
dependencies and dropping and recreating dependent views on schema
changes. This might be a better job for one of the GUI tools for us
too, rather than trying to put it in the back end. Brand X doesn't do
it in their backend either.

On 8/25/05, Jim C. Nasby <jnasby(at)pervasive(dot)com> wrote:
> On Thu, Aug 25, 2005 at 03:03:30PM -0700, CSN wrote:
> > For lack of a better term, but I was curious if there
> > is/was any thought about making PG's views
> > automatically "see" changes in underlying tables, as
> > opposed to currently having to drop/create all
> > corresponding views if a table's structure (add/delete
> > fields, etc.) is changed.
>
> There's not currently a TODO for this, no.
> http://www.postgresql.org/docs/faqs.TODO.html I'm not sure how hard it
> would be to do, since currently CREATE VIEW v AS SELECT * FROM t
> actually expands the * out at creation time.
> --
> Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
> Pervasive Software http://pervasive.com 512-569-9461
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message felix 2005-08-26 05:11:33 Re: unsubscribe
Previous Message Tom Lane 2005-08-26 03:54:26 Re: POSS. FEATURE REQ: "Dynamic" Views