Re: Rules and Views - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Rules and Views
Date
Msg-id 1028089009.1950.71.camel@rh72.home.ee
Whole thread Raw
In response to Re: Rules and Views  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Rules and Views  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, 2002-07-31 at 10:22, Tom Lane wrote:
> Curt Sampson <cjs@cynic.net> writes:
> > On Wed, 31 Jul 2002, Tom Lane wrote:
> >> Well, to my mind that's what the error message says now.  The reason
> >> it didn't help you was that you *did* have a rule ... but it didn't
> >> completely override the view insertion.
> 
> > Right, like I said, my model was wrong. I didn't think of the error
> > message as being an "insert behaviour" that had to be overridden; I
> > thought of it as a "there is no behaviour right now" message.
> 
> Hm.  How about
> 
> ERROR:  Cannot insert into a view
>     You need an unconditional ON INSERT DO INSTEAD rule

Seems more accurate, but actually you may also have two or more
conditional rules that cover all possibilities if taken together.

Maybe

ERROR:  Cannot insert into a view       You need an ON INSERT DO INSTEAD rule that matches your INSERT

Which covers both cases.

-----------------
Hannu



pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: WAL file location
Next
From: Tom Lane
Date:
Subject: Re: Why is MySQL more chosen over PostgreSQL?