--On Montag, Januar 26, 2009 20:03:41 -0800 Josh Berkus <j...@agliodbs.com>
wrote:
Jaime, Bernd,
having said that, i don't think that inventing new syntax is the way
to go... a reloption seems better (thinking a little more, it could be
a problem if the user changes the reloptions of an already created
view)
There's also the issue with backup/restore: we need some kind of syntax
for restoring a read-only view which doesn't depend on command ordering.
So we need a ALTER VIEW SET READ ONLY or similar.
Hence my proposal with
CREATE [OR REPLACE] [READ ONLY|UPDATABLE] VIEW
This can easily be extended to ALTER VIEW SET [READ ONLY|UPDATABLE].
Besides other issues already mentioned, this looks more logical to me,
since this is going to change the behavior of a view completely.
--
Thanks
Bernd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
