| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:22:56 |
| Message-ID: | 497E37C0.1070505@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Bruce Momjian wrote:
> 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.
I'd frankly look at WITH, which is where we've historically stuck
non-SQL extensions.
> BTW, how do we handle cases where the query cannot be updatable, e.g.
> aggregates? Do we throw a warning?
>
Error if "updatable" is specified, warning if not.
--Josh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-01-27 00:56:14 | Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle |
| Previous Message | Jaime Casanova | 2009-01-26 22:21:08 | Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Mayer | 2009-01-26 22:42:32 | Re: 8.4 release planning |
| Previous Message | Jaime Casanova | 2009-01-26 22:21:08 | Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle |