From: "Joel Burton" <jburton@scw.org>
Organization: Support Center of Washington
To: Tom Lane <tgl@sss.pgh.pa.us>
Date: Tue, 5 Dec 2000 15:26:37 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Rules with Conditions: Still Doesn't Work (Bug Rpt) 
CC: pgsql-bugs@postgresql.org, pgsql-docs@postgresql.org
Message-ID: <3A2D092D.14054.15DCFC7@localhost>
References: <3A2B7D2B.27409.3A1124@localhost> 
In-reply-to: <17797.976044068@sss.pgh.pa.us>

> It turns out that all of these failures come from the same place,
> which is that I had broken the handling of INSERT ... SELECT actions
> inside rules.
> 
> I have committed a patch that appears to fix the problem.
> I think that Marc has already tagged beta1, however, so the patch will
> not be in the beta1 tarball due to appear Real Soon Now. You can pull
> current sources from the CVS server, or grab a nightly snapshot
> tarball after tonight.

Fast work! (Boy, I sure wish I had a commercial Oracle/M$ contract 
instead. I'm sure they could have done it faster ;-) ). Thanks!

Just to be clear (as much for other as for me): this should fix the 
syntax as my (more recent) bug report submitted? That is, one non-
conditional rule that tries to handle both inserting and updating 
together, as opposed to 2 different conditional rules that, together, 
try to handle all cases.
 
> Thanks for the detailed, easy-to-reproduce bug example!  These sorts
> of reports are by far the nicest from a developer's point of view ;-)

My Mom always said I loved finding problems. :-)


--
Joel Burton, Director of Information Systems -*- jburton@scw.org
Support Center of Washington (www.scw.org)