If I redefine the foreign keys in a different order (e.g. C, D, B) the
delete rule for the first one is correct ("SET NULL"), but the second
one is wrong again. It is the same for "CASCADE" except "SET NULL".
well, did you test it? this sounds like an old SQL-Studio bug
BTW: is the current version of SQL-Studio showing the foreign-keys correctly already?
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
