Re: Why does an ON SELECT rule have to be named "_RETURN"? - Mailing list pgsql-general

From Peter Eisentraut
Subject Re: Why does an ON SELECT rule have to be named "_RETURN"?
Date
Msg-id 200602130749.43496.peter_e@gmx.net
Whole thread Raw
In response to Re: Why does an ON SELECT rule have to be named "_RETURN"?  ("Ken Winter" <ken@sunward.org>)
Responses Re: Why does an ON SELECT rule have to be named "_RETURN"?  (Robert Treat <xzilla@users.sourceforge.net>)
List 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/

pgsql-general by date:

Previous
From: indu ss
Date:
Subject: Re: Compile of Pgmail function fails
Next
From: Tom Lane
Date:
Subject: Re: "out of shared memory error" with temp tables