Re: [HACKERS] FOREIGN KEY !!!!!

> o Under RESTRICT, by contrast, the system realizes "ahead of
>   time" that row R2 exists and will violate the constraint if
>   R1 is deleted, and so rejects the DELETE out of hand.
   That'd mean in last consequence, that RESTRICT actions aren't   DEFERRABLE, while the rest of their constraint
definitionis!   Anyway,  cannot  work  with  the actual implementation of the   trigger queue, so we could either make
RESTRICTand NO ACTION   identical (except for different ERROR messages), or leave the   SQL3 RESTRICT out of 7.0 while
changingNO ACTION to fire the   message.
 
   I'd  prefer  to have them identical in 7.0, because according   to Date they have no semantic difference,  so  it'll
buy  us   little  if we complicate the trigger stuff more than required   right now.
 


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #