Re: problem with parent/child table and FKs

On Thursday, April 21, 2011 4:36:51 am Karsten Hilbert wrote:
> Does anyone have any suggestions regarding the below ?

The only thing I can come up with is to eliminate the FK :
 fk_code integer not null
               references code_root(pk_code_root)
               on update restrict
               on delete restrict
on lnk_codes2epi and replace it with a trigger that essentially does the same
thing ; check for presence of pk_code_root.

>
> Thanks,
> Karsten
>


--
Adrian Klaver
adrian.klaver@gmail.com