Re: Help with Mutating Table - Are there other solutions?

On Sat, 13 Dec 2003 11:39:23 -0500, contrapositive wrote:

> Two tables, ORDERS and DETAIL_LINES:
>
> ORDERS.order_id
> ORDERS.cust_id
> ORDERS.order_status, etc...
>
> DETAIL_LINES.order_id
> DETAIL_LINES.line_id
> DETAIL_LINES.line_status, etc...
>
> An order has one or more detail lines.
>
> We want an update trigger (for each row) on DETAIL_LINES that says if this
> line_status is being changed to HOLD, then all the other lines for this
> order should change to HOLD. Obviously, that means we're attempting to
> update the table that's being triggered, and the "mutating table" error is
> raised.

Seems you are using triggers to fix design redundancy. Why is HOLD reflected in the line_status, if it can only be set for the whole order?

You can use the trigger approach to fix this, but in the long run it will come back again to cause trouble.

Sincerely,
Joachim

-- 
Warnung: \" kann Augenkrebs verursachen.