On Monday 21 November 2005 08:16 pm, David Fetter wrote: > On Mon, Nov 21, 2005 at 08:05:19PM -0500, Jerry Sievers wrote: > > Chris Kratz <chris.kratz@xxxxxxxxxxxxxx> writes: > > > Hello All, > > > > > > We have finally tracked down a bug in our application to a rewrite rule > > > on a table. In essence, the rewrite rule in question logs any inserts > > > to another table. This works correctly in all cases except where an > > > "except" clause is used in the insert statement. In this case, the > > > rows are inserted into the primary table as expected, but the rule > > > either does not fire, or fires in such a way that nothing is placed in > > > the changes table. > > > > You must be referring to something like; > > > > insert into foo > > select * > > from sometable > > except > > select * > > from someothertable > > ; > > > > If there's an EXCEPT clause on INSERT, I've never seen it. > > I suppose you could wrap the SELECT...EXCEPT in parens. > > WARNING Untested Code: > > INSERT INTO foo > (SELECT a,b,c FROM bar > EXCEPT > SELECT a,b,c FROM baz); > > HTH :) > > Cheers, > D Hello David, Yes, we actually did try the parenthesis, but we still observed the same behavior. Thanks though, -Chris -- Chris Kratz
