Re: POSS. FEATURE REQ: "Dynamic" Views
От | Jim C. Nasby |
---|---|
Тема | Re: POSS. FEATURE REQ: "Dynamic" Views |
Дата | |
Msg-id | 20050826215148.GK11282@pervasive.com обсуждение исходный текст |
Ответ на | Re: POSS. FEATURE REQ: "Dynamic" Views (Greg Stark <gsstark@mit.edu>) |
Ответы |
Re: POSS. FEATURE REQ: "Dynamic" Views
|
Список | pgsql-general |
On Fri, Aug 26, 2005 at 04:54:06PM -0400, Greg Stark wrote: > > Ian Harding <harding.ian@gmail.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. 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? -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com 512-569-9461
В списке pgsql-general по дате отправления: