You have to drop the constraint and recreate it with the ON DELETE CASCADE
option. Since you have sensibly named your constraint,
you can easily drop it and then use the alter table statement to add the
constraint with theON DELETE CASCADE option
wolfgang karrer wrote in message <38e9d7b0_at_alijku02.edvz.uni-linz.ac.at>...
>Hi everyone,
>
>
>how is it possible to change a foreign key constraint to do the on delete
>cascade?
>
>CREATE TABLE Verfahren
> (verfahrenNr INTEGER PRIMARY KEY,
> bezeichnung VARCHAR2(50) NOT NULL,
> beschreibung VARCHAR2(500),
> ziel VARCHAR2(500),
> datumerstellt DATE,
> erhebNr INTEGER NOT NULL,
> CONSTRAINT erhebNr_verfahren FOREIGN KEY (erhebNr) REFERENCES
>ERHEBUNGSMETHODE (erhebNr));
>
>This is the table i created for a few years. Now i want to add a on delete
>cascade to the constraint erhebnr_verfahren. How is this possible?
>
>ALTER TABLE Verfahren modify ...
>
>Thanks a lot
>
>
>
>--
>Wolfgang Karrer
>Büro für EDV-Dienstleistungen
>Gewerbegasse 6
>4060 Leonding
>Tel + Fax. (0732) 681795
>Mobil: (0699) 134 18 469
>EMail: w.karrer_at_ooenet.at
>---------------------------------------
>Institut für Wirtschaftsinformatik
>Abteilung Communications Engineering
>o.Univ.- Prof. DI Dr. Christian Stary
>Freistädterstr. 315
>4040 Linz/Urfahr
>Tel: (0732) 2468-7112
>EMail: wolfgang.karrer_at_ce.uni-linz.ac.at
>
>
>
Received on Tue Apr 04 2000 - 07:14:33 CDT
