Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Deferred uniqueness versus foreign keys


  • From: Dean Rasheed <dean(dot)a(dot)rasheed(at)googlemail(dot)com>
  • To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: Deferred uniqueness versus foreign keys
  • Date: Tue, 28 Jul 2009 22:10:54 +0100
  • Message-id: <8e2dbb700907281410m3e73ec93p2dd1f0ad3dbb8f53@mail.gmail.com> <text/plain>

2009/7/28 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> [sigh, forgot to cc hackers the first time ]
>
> Foreign key behavior is only sane if the referenced column(s) are
> unique.  With the proposed patch, it is possible that the uniqueness
> check on the referenced columns is deferred, which means it might not
> occur till after an FK check does.  Discuss.
>
>                        regards, tom lane
>

Hmm, yes, looking in the SQL spec, I've just noticed this under 11.8,
referential constraint definition:

"The table constraint descriptor describing the <unique constraint
definition> whose <unique column list> identifies the referenced
columns shall indicate that the unique constraint is not deferrable."

which seems like a sensible policy now that I think about it.

 - Dean



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group