On the FK cascade delete, why is it implemented where the definition is specified on the "many" side of a one-to-many. If I have tables GROUP and GROUPITEMS and need the related group items deleted when a particular GROUP is deleted, wouldn't it make since to define this in the GROUP table? If I were going to use a trigger, this is where it would go (I assume this as I haven't messed with triggers on SAPDB yet). I am just curious about this as it seems counter-intuitive and I spent much time trying to get this relation set up. Which bring me to:
As a foreign-key only implicitly affects the refereced table, but heavily affects the referencing table (the table on "many" side) - for example by deleting columns - it does make sense to me.
Of course, triggers would have to be defined for the referenced table, but this is just because you have to trigger events happening in that table.
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
