DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=uZJ+IsIPiixXemC+P40i1AqeQbwF411Lr9Cjil3Wo7XNjtSUzWXiBncKKaeTphmWiSO9VloqwLmg6RlPlN/KcnzuePePSYQmZBX5SXn+rtCgpbl7Cw+ThMB3dE64HbBzrTIIpzKdcIqwv7vKIm+uXdfh2Nn3OPCzHjX0mU+hu8c=
Message-ID: <4f4c2a010703272051g94d88fdkc508a1b1ef189b34@mail.gmail.com>
Date: Tue, 27 Mar 2007 23:51:35 -0400
From: "Jon Horsman" <horshaq@gmail.com>
To: pgsql-sql@postgresql.org
Subject: Re: Foreign Unique Constraint
In-Reply-To: <002501c770bd$a42f94a0$9b0014ac@wbaus090>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4f4c2a010703270621h5137a4e5rb515a9be9034a543@mail.gmail.com>
	<002501c770bd$a42f94a0$9b0014ac@wbaus090>

> Perhaps this...? It would work, but depending how many rows are in the
> table, it could become incredibly slow.

The max rows in either table would be about 1000 or so, which isn't
too many.  There also should be a hole lot of inserting going on.

> ALTER TABLE table1 ADD CHECK (extension NOT IN (SELECT extension FROM
> table2));

I guess this is the functionality i was looking for but was hoping
there would be a cleaner way to do it.

Anyways, thanks to everyone who replied.  I'll look into each of the
proposed solutions to see what best suits my needs.  If anyone has a
different solution i'd still like to hear it.

Jon