Tom Lane wrote:
Jeff Boes <[EMAIL PROTECTED]> writes:
It appears that the rule is inserting the row copies into
job_queue_trace with a job_id value that is one higher than the job_id
from the original row. Almost as though it was re-evaluating the
sequence ...
No kidding. A rule is a macro and therefore has the usual risks of
multiple evaluations of arguments.
The only way to do what you want is with a trigger.
regards, tom lane
But shouldn't "new.job_id" use the value that was already recorded in
the original row? I'm not using --
INSERT INTO job_queue_trace (job_id) VALUES (nextval(...))
but
INSERT INTO job_queue_trace (job_id) VALUES (new.job_id)
Why is the sequence involved?
--
Jeff Boes vox 269.226.9550 ext 24
Database Engineer fax 269.349.9076
Nexcerpt, Inc. http://www.nexcerpt.com
...Nexcerpt... Extend your Expertise
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend
