Skip site navigation (1) Skip section navigation (2)

Re: Rules and Views

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Curt Sampson <cjs(at)cynic(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Rules and Views
Date: 2002-07-31 04:16:49
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Wed, 2002-07-31 at 10:22, Tom Lane wrote:
> Curt Sampson <cjs(at)cynic(dot)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.


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

Which covers both cases.


In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2002-07-31 04:17:12
Subject: Re: WAL file location
Previous:From: Tom LaneDate: 2002-07-31 04:14:32
Subject: Re: Outer join differences

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group