Re: POSS. FEATURE REQ: "Dynamic" Views

From: Greg Stark <gsstark(at)mit(dot)edu>
To: iharding(at)destinydata(dot)com
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(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-26 20:54:06
Message-ID: 87acj4a07l.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Ian Harding <harding(dot)ian(at)gmail(dot)com> writes:

> Brand X doesn't do it in their backend either.

If your Brand X is the same as my Brand X then it's worth noting that they
didn't previously do anything sane in their backend. It used to invalidate all
your views and you had to recompile them before they would work again.

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.

--
greg

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message vishal saberwal 2005-08-26 20:57:36 Re: PQConnectdb SSL (sslmode): Is this a bug
Previous Message Bruce Momjian 2005-08-26 20:41:47 Re: Postgresql Function Cookbook/General howto