Re: deleting the master but not the detail

Поиск
Список
Период
Сортировка
Искать
От
Ismael ....
Тема
Re: deleting the master but not the detail
Дата
Msg-id
BLU103-W293F5FFBECA7C4F53839A9A38E0@phx.gbl
Ответ на
Список
Дерево обсуждения
deleting the master but not the detail "Ismael ...." <ismaelpsp@hotmail.com>
Re: deleting the master but not the detail "A. Kretschmer" <andreas.kretschmer@schollglas.com>
Re: deleting the master but not the detail Raymond O'Donnell <rod@iol.ie>
Re: deleting the master but not the detail "Ismael ...." <ismaelpsp@hotmail.com>
Re: deleting the master but not the detail Stephan Szabo <sszabo@megazone.bigpanda.com>
Re: deleting the master but not the detail "Ismael ...." <ismaelpsp@hotmail.com>
Re: deleting the master but not the detail "Douglas McNaught" <doug@mcnaught.org>
Re: deleting the master but not the detail "Scott Marlowe" <scott.marlowe@gmail.com>
Re: deleting the master but not the detail "Ismael ...." <ismaelpsp@hotmail.com>
Re: deleting the master but not the detail "Webb Sprague" <webb.sprague@gmail.com>

So is there no other way to do it but to verify the integrity using triggers
and drop the referential constraints?

Because I *still* need to verify that NEW records in the details table
direct to something that exists


> 
>> ON DELETE RESTRICT | NO ACTION won't let me delete the master
>> CASCADE | SET NULL | SET DEFAULT will modify the details
> 
> Can you just drop the constraint that's doing the referential integrity?
> 
> Ray.
> 
> Then remove the referential integrity constraint, since it's obviously
> incompatible with your business requirements.
>  
> -Doug
_________________________________________________________________
Plug&Play te trae en exclusiva los mejores conciertos de la red
http://club.prodigymsn.com/ 
В списке pgsql-general по дате отправления
От: Raymond O'Donnell
Дата:
От: Douglas McNaught
Дата:
FAQ