Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5QEfka86886 for ; Tue, 26 Jun 2001 10:41:46 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f5QEfKF03078; Tue, 26 Jun 2001 10:41:21 -0400 (EDT) To: Luis Sousa cc: pgsql sql Mailing List Subject: Re: Problems using a rule with the WHERE clause In-reply-to: <3B385B5E.A8A31C59@ualg.pt> References: <3B3753FB.2E1BA9B0@ualg.pt> <16743.993492071@sss.pgh.pa.us> <3B385B5E.A8A31C59@ualg.pt> Comments: In-reply-to Luis Sousa message dated "Tue, 26 Jun 2001 10:52:30 +0100" Date: Tue, 26 Jun 2001 10:41:20 -0400 Message-ID: <3075.993566480@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/417 X-Sequence-Number: 3714 Luis Sousa writes: > I think this code is OK !!!!! You probably don't want the second and third rules to be INSTEAD. However, > But I got the error message bellow in line 11 > of my script, that corresponds to the rule updateturnodocente_default > > psql:dev/pessoal/def/views_rules/teste_update:11: pqReadData() -- backend > closed the channel unexpectedly. that shouldn't happen, in any case. If this is the current release (7.1.2) then I'd like to see a complete script to reproduce the problem. (I don't have time to guess at your table declarations...) regards, tom lane