Re: idea: storing view source in system catalogs
От
Tom Lane
Тема
Re: idea: storing view source in system catalogs
Дата
Msg-id
29732.1211463102@sss.pgh.pa.us
Ответ на
Re: idea: storing view source in system catalogs (Robert Haas)
Список
Дерево обсуждения
idea: storing view source in system catalogs "Merlin Moncure" <mmoncure@gmail.com>
Re: idea: storing view source in system catalogs David Fetter <david@fetter.org>
Re: idea: storing view source in system catalogs Florian Pflug <fgp.phlo.org@gmail.com>
Re: idea: storing view source in system catalogs Andreas Pflug <pgadmin@pse-consulting.de>
Re: idea: storing view source in system catalogs Hannu Krosing <hannu@krosing.net>
Re: idea: storing view source in system catalogs "Merlin Moncure" <mmoncure@gmail.com>
Re: idea: storing view source in system catalogs "Robert Haas" <robertmhaas@gmail.com>
Re: idea: storing view source in system catalogs Bruce Momjian <bruce@momjian.us>
Re: idea: storing view source in system catalogs Tom Lane <tgl@sss.pgh.pa.us>
Re: idea: storing view source in system catalogs Gregory Stark <stark@enterprisedb.com>
Re: idea: storing view source in system catalogs Tom Lane <tgl@sss.pgh.pa.us>
Re: idea: storing view source in system catalogs Tom Lane <tgl@sss.pgh.pa.us>
"Robert Haas" writes: > I think the real problem here is that PostgreSQL is very finicky about > what operations you can perform on a view. If I have a table foo and > I define a view bar that uses foo and a view baz that uses bar, I can > add a column to foo without a problem, and, similarly, I can also drop > or alter a column in foo that is not used by bar. But the same is not > true of bar. Yeah. The current restrictions were set when CREATE OR REPLACE VIEW was first implemented, and at that time we didn't have very much ALTER TABLE capability at all; the view restrictions mirror what we could do with a table at the time. It would be worth revisiting that to make it square up with what you can now do to a table. regards, tom lane
В списке pgsql-hackers по дате отправления