Re: Why does an ON SELECT rule have to be named "_RETURN"?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-general(at)postgresql(dot)org, ken(at)sunward(dot)org
Subject: Re: Why does an ON SELECT rule have to be named "_RETURN"?
Date: 2006-02-13 06:49:43
Message-ID: 200602130749.43496.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ken Winter wrote:
> have a harder row to hoe: They have to figure out whether a view
> really IS updatable - most presumably aren't, so if they provide
> forms that offer to update views, most of the time these forms are
> going to crash.

First of all, it isn't all that hard to figure out whether a view is
probably updatable (the presence of the respective rules would be a
strong hint). And second, if it's not, you get a fine error message
and can move on. So there is really no good reason for client tools to
prevent you from using data entry forms on views.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-02-13 06:56:22 Re: "out of shared memory error" with temp tables
Previous Message indu ss 2006-02-13 05:22:59 Re: Compile of Pgmail function fails