Re: Foreign keys - Mailing list pgsql-hackers

From Stefan Kaltenbrunner
Subject Re: Foreign keys
Date
Msg-id 4503D047.2090302@kaltenbrunner.cc
Whole thread Raw
In response to Foreign keys  ("MAR - Secretariado Geral" <secretariadogeral@acra.pt>)
List pgsql-hackers
MAR - Secretariado Geral wrote:
> Hi everybody,
>  
> First of all i'de like to apolagize cause my poor english. After this, i
> shuould say that i beleavee a year ago i brought this problem to the
> community but i donn't remember some answering about it. The problem is:
>  
> Every time a users misses a external refrenced key the PGSql raises an
> exception.
> Well as far as i realise if we had 5 or 10 Foreign keys
> during an Insert/Update transaction only exception should be raised
> reporting all erros/messages after last external refrenced field missed
> at one time,not one by one.
> Well, in order to implement this idea we will need to desable the
> built-in refencial integrety and build it all by your self- all the
> validation (look-ups etc..) before insert/update If tg_op='insert' or
> tg_op='update'  then as people do with non relational Databases - all
> hand-made. Well, this is very hard to beleave!!! I must be missing
> something.
>  
> Please i'must be wrong can some one explain me what i'm missing?

I'm not sure what you are complining about exactly but maybe you want to
declare your FK as DEFERRABLE INITIALLY DEFERRED ?
That way the constraint checking happens at the end of the transaction
and not immediately


Stefan


pgsql-hackers by date:

Previous
From: Chris Mair
Date:
Subject: Re: Foreign keys
Next
From: Gregory Stark
Date:
Subject: Re: Foreign keys