
> > FOREIGN KEY INSERT & UPDATE/DELETE in transaction "change violation"
> 
>     A well known issue, and I've asked multiple times how exactly
>     we want to define the behaviour for deferred constraints.  Do
>     foreign keys reference just to a key value and are happy with
>     it's existance, or do they refer to a particular row?

Sorry, to answer late. I didn't know this needed clarification.
The answer is simple, foreign keys only reference a key value,
not a particular row.

Andreas

Fri, 26 Jan 2001 18:52:33 +0100
Zeugswetter Andreas SB  <ZeugswetterA@wien.spardat.at>
AW: Open 7.1 items
Zeugswetter Andreas SB  <ZeugswetterA@wien.spardat.at> writes:
> FOREIGN KEY INSERT & UPDATE/DELETE in transaction "change violation"
>> 
>> A well known issue, and I've asked multiple times how exactly
>> we want to define the behaviour for deferred constraints.  Do
>> foreign keys reference just to a key value and are happy with
>> it's existance, or do they refer to a particular row?

> Sorry, to answer late. I didn't know this needed clarification.
> The answer is simple, foreign keys only reference a key value,
> not a particular row.

Cite chapter and verse in the spec, please?

			regards, tom lane

Fri, 26 Jan 2001 16:30:42 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: AW: Open 7.1 items 