Jaime Casanova wrote: > On Mon, Jan 26, 2009 at 5:18 PM, Bruce Momjian <br...@momjian.us> wrote: > > Tom Lane wrote: > >> Bernd Helmle <maili...@oopsware.de> writes: > >> > Or what about > >> > CREATE [OR REPLACE] [UPDATABLE] VIEW ... ? > >> > This looks closer to TEMP|TEMPORARY VIEW, which we already have. > >> > >> But per spec, UPDATABLE should be the default (if not now, then > >> eventually). Are you proposing > >> CREATE [OR REPLACE] [[NOT] UPDATABLE] VIEW ... > >> ? Seems confusing. > > > > UNUPDATABLE? :-) > > > > BTW, how do we handle cases where the query cannot be updatable, e.g. > > aggregates? Do we throw a warning? > > > > yes. we detect that and send a warning saying that there not be any rules
OK, so we are going to need an option to suppress that warning, even without the problems of upgrades and customization. We already use READ ONLY in SET TRANSACTION and START TRANSACTION, so it would be logical to use READ ONLY to control this. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
