I do not think you can use trigger approach, since you are going to get
a famous "trigger constrainig" error message.
The reason why it is so difficult is because Oracle still has not
implemented
cascade update.
The only choice you have (IMHO) is to insert new record in PAYMENT
with new PersonID and other fields the same as for th eold PersonID,
then copy all exisiting records in CREDIT under old PersonID to new PersonID
then delete the old PersonID records from PAYMENT and if you have
delete cascade it will delete all corresponding children. If you do not have
cascade
delete defined, then delete children first manually.
Regards,
George
Received on Thu Dec 03 1998 - 16:07:46 CST
