| From: | Jerry Sievers <jerry(at)jerrysievers(dot)com> | 
|---|---|
| To: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: Rule appears not to fire on insert w/ "except" | 
| Date: | 2005-11-22 01:05:19 | 
| Message-ID: | m3wtj1cx0w.fsf@prod01.jerrysievers.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
Chris Kratz <chris(dot)kratz(at)vistashare(dot)com> 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.
Perhaps you should post your insert query and your rule declaration.
>  As a side note, is there a way to see the final sql after all "rewrite" rules 
> have been processed?  It might help us understand what is going on.  
Not SQL but see config setting;
debug_print_rewritten
-- 
-------------------------------------------------------------------------------
Jerry Sievers   305 854-3001 (home)     WWW ECommerce Consultant
                305 321-1144 (mobile	http://www.JerrySievers.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2005-11-22 01:16:32 | Re: Rule appears not to fire on insert w/ "except" | 
| Previous Message | Michael Glaesemann | 2005-11-22 01:04:52 | Re: Best way to represent values. |