From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200310082230.h98MUIf08911@candle.pha.pa.us>
Subject: Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta)
In-Reply-To: <3F79CE69.3040203@Yahoo.com>
To: Jan Wieck <JanWieck@Yahoo.com>
Date: Wed, 8 Oct 2003 18:30:18 -0400 (EDT)
Cc: Stephan Szabo <sszabo@megazone.bigpanda.com>,
 Tom Lane <tgl@sss.pgh.pa.us>,
	Christopher Kings-Lynne <chriskl@familyhealth.com.au>,
	Peter Childs <Blue.Dragon@blueyonder.co.uk>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Jan Wieck wrote:
> > I think this is a larger argument than the one that was being discussed
> > above. Given a dump of objects I own, can I restore them without requiring
> > the fk check to be done if I alter table add constraint a foreign key? If
> > the answer to that is no, then the option can be put in as a superuser
> > only option and it's relatively easy. If the answer to that is yes, then
> > there are additional issues that need to be resolved.
> 
> Well, with the CREATE CONSTRAINT TRIGGER you _can_, but we already have 
> a consensus that we don't _want_ that. Probably we should declare it 
> deprecated and remove it in 7.5. And the option currently under 
> discussion is exactly what will cause ALTER TABLE to let you, but IMHO 
> that _should_ be restricted.

Added to TODO:

	* Remove CREATE CONSTRAINT TRIGGER

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073