From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
---|---|
To: | mladen(dot)gogala(at)vmsinfo(dot)com |
Cc: | joseflores <jose(dot)floresv(at)gmail(dot)com>, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Unable to use VIEWS (Ok button remains shaded) |
Date: | 2010-09-17 03:53:44 |
Message-ID: | AANLkTin3rYqtMb=W30+1ewo_=EhWp7P_7A6F4Egqp93-@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Thu, Sep 16, 2010 at 7:00 PM, Mladen Gogala
<mladen(dot)gogala(at)vmsinfo(dot)com> wrote:
> I always wandered why would anybody want to update a view? View is, by
> definition, a stored query which is executed frequently enough to be given
> its own first name, middle name and a family name.
I understand the practicality of what you're saying. However, I'm
curious about where your definition of views comes from. My
understanding is that update-able views were concepts of Codd's
original relational model and such views are also part of the SQL
standard.
And since "PostgreSQL prides itself in standards compliance...,"
(http://www.postgresql.org/about/) I wouldn't expect to see
update-able views on the features *not* to do list any time soon.
(http://wiki.postgresql.org/wiki/Todo#Features_We_Do_Not_Want)
Although I do see planner hints are one of the features listed there.
--
Regards,
Richard Broersma Jr.
Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
From | Date | Subject | |
---|---|---|---|
Next Message | Salil Wadnerkar | 2010-09-17 10:14:35 | Re: transaction is read-only error |
Previous Message | Mladen Gogala | 2010-09-17 02:00:32 | Re: Unable to use VIEWS (Ok button remains shaded) |