Another question related to this...
> >CREATE TABLE "DBA"."SPECIALISTMANAGERLINK"
> >(
> > "SPECIALISTID" Varchar (6) ASCII,
> > "MANAGERID" Varchar (6) ASCII,
> > PRIMARY KEY ("SPECIALISTID", "MANAGERID"),
> > FOREIGN KEY "SPECIALISTMANAGERLINK_SPECIALI" ("SPECIALISTID") REFERENCES
"DBA"."SPECIALIST" ("SPECIALISTID") ON DELETE CASCADE,
> > FOREIGN KEY "SPECIALISTMANAGERLINK_MANAGERI" ("MANAGERID") REFERENCES
"DBA"."SPECIALIST" ("SPECIALISTID") ON DELETE RESTRICT
> )
>
> The update rule of SAPDB implicitly is 'ON UPDATE RESTRICT', i.e. the
update of a master row fails
> if any child rows exists.
> 'ON UPDATE CASCADE' is not implemented.
> You can simulate the key update if you delete the row and insert it again
with the new key.
>
> Thomas
...Does this mean that also a trigger created for that column (AFTER UPDATE
("SPEC...") EXECUTE would fail?
thx, Sascha
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
