I think the best way is to modify the FOREIGN KEY definition in the tables 1
and 2 adding the 'ON DELETE CASCADE' condition.
ALTER TABLE 1 ADD FOREIGN KEY (fkCol) references 2(pkCol) on DELETE CASCADE;
ALTER TABLE 2 ADD FOREIGN KEY (fkCol) references 3(pkCol) on DELETE CASCADE;
Aloha!
Hi Chandra,
you have two possible situations:
Case (A) you can delete 'astro_tbl' rows with NO particular actions
Case (B1) you must alter 'astro_tbl' table adding a cascade costraint to have
the system delete rows in the 'astro_tbl' table when one row in 'authen_tbl'
table is being deleted if
