| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bernd Helmle <mailings(at)oopsware(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle |
| Date: | 2009-01-26 22:18:56 |
| Message-ID: | 200901262218.n0QMIu423706@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Tom Lane wrote:
> Bernd Helmle <mailings(at)oopsware(dot)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?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2009-01-26 22:21:08 | Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle |
| Previous Message | Alvaro Herrera | 2009-01-26 19:41:06 | pgsql: Allow extracting and parsing of reloptions from a bare pg_class |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2009-01-26 22:21:08 | Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle |
| Previous Message | Ron Mayer | 2009-01-26 22:18:20 | Re: 8.4 release planning |