Re: Trigger problem

From: Jagdeep Shiruru <jagdeep_at_cc.bellcore.com>
Date: 1996/06/11
Message-ID: <4pkgqi$1lp_at_athos.cc.bellcore.com>#1/1


In article <4pbn75$u13_at_opera.iinet.net.au>, mapsonp_at_ois.com.au (Peter Mapson) writes:
|> You don't supply the full code for your trigger, so forgive me if I'm
|> stating the obvious, but...
|>
|> Is the trigger defined as "before update on <table>", or "before
|> update on <table> for each row". The first type of trigger only fires
|> once, regardless of how many rows are being updated. The second type
|> of trigger fires once for each row updated.
|>

I am sorry that I did not give the full details. I am doing an BEFORE UPDATE with the FOR EACH ROW option in the trigger header. I get most of the data through the pipe, but 2 or 3 are missed. That is if an update is done on 10 rows, the receiver end in the Pro*C prints 7 or 8 rows. This happens randomly and is inconsistent. It is not the same row that gets missed all the time, but different rows. Hope I am clear. Thanks for pointing that out.

Jagdeep Received on Tue Jun 11 1996 - 00:00:00 CEST

Original text of this message