Re: Cascade Update Trigger Problems

dleenhouts_at_gmail.com schreef:
> My apologies, this is my first time posting. Maybe the folks at Google
> can switch the default for replying...
>
It is, actually, when using the option link to answer.

> I've got a whole lot of constraints (upwards of 70 or 80 child tables),
> & roughly 40 or 50 sets of companies to merge, so I really don't want
> to write a separate update line for every child table. Would creating a
> trigger be helpful in updating those? Then I can do individual update
> commands like
>
> update company set companykey = 1 where company key in (2, 3, 4);
>
> for each set of companies, & then the trigger will update all the child
> tables?
>

I still do not quite understand the nature of your problem; you say you have the from/to sets.
OK - so store these in a table, and use 1 simple sql statement to update the main table, using the from/to table as lookup.

I probably show my misunderstanding the problem by not getting the need for a cascading update?

-- 
Regards,
Frank van Bortel

Top-posting is one way to shut me up...