Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229])
	by mail.postgresql.org (Postfix) with ESMTP id 5694118E38D9
	for <pgsql-sql@postgresql.org>; Thu, 12 Jan 2012 13:10:23 -0400 (AST)
Received: from mail-gy0-f174.google.com ([209.85.160.174])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <adrian.klaver@gmail.com>) id 1RlOAO-0002Eh-Bf
	for pgsql-sql@postgresql.org; Thu, 12 Jan 2012 17:10:22 +0000
Received: by ghbg16 with SMTP id g16so396156ghb.19
	for <pgsql-sql@postgresql.org>; Thu, 12 Jan 2012 09:10:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=from:to:subject:date:user-agent:cc:references:in-reply-to
	:mime-version:content-type:content-transfer-encoding:message-id;
	bh=fXp56NFhidYNNBqyIdtiQmBVmYrSY1MrZ8ZoF+zeUjQ=;
	b=sSDWTcY16it+LyA/nntNBt9kilNKdk1EnVe6FpgtPFwnqc/C6Lm0UWA4507t3U9YZg
	2IW3wgUurNDzv1FquMbsWiwy+5DrNQcgiQ5ifr2n2LyOSLFQ/+KKyUlKmGVN5QY2W2kK
	gBnuvrxLnZr+xSwITzff0QjOCNordTU0lpN4c=
Received: by 10.50.182.130 with SMTP id ee2mr4871308igc.30.1326388207287;
	Thu, 12 Jan 2012 09:10:07 -0800 (PST)
Received: from tucker.localnet (c-24-17-164-54.hsd1.wa.comcast.net.
	[24.17.164.54])
	by mx.google.com with ESMTPS id z22sm19216921ibg.5.2012.01.12.09.10.05
	(version=SSLv3 cipher=OTHER); Thu, 12 Jan 2012 09:10:06 -0800 (PST)
From: Adrian Klaver <adrian.klaver@gmail.com>
To: "David Johnston" <polobo@yahoo.com>
Subject: Re: Unable To Modify Table
Date: Thu, 12 Jan 2012 09:10:02 -0800
User-Agent: KMail/1.13.5 (Linux/2.6.32-37-generic; KDE/4.4.5; i686; ; )
Cc: pgsql-sql@postgresql.org,
 "'Carlos Mennens'" <carlos.mennens@gmail.com>
References: 
 <CAAQLLO70j_j-nz7sZmXbcKT7QRmuf6oQRsCT_N5=+8UC7NFp1A@mail.gmail.com>
	<201201120854.42306.adrian.klaver@gmail.com>
	<017101ccd14b$fbc0f120$f342d360$@yahoo.com>
In-Reply-To: <017101ccd14b$fbc0f120$f342d360$@yahoo.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201201120910.02794.adrian.klaver@gmail.com>
X-Pg-Spam-Score: -2.7 (--)
X-Archive-Number: 201201/51
X-Sequence-Number: 36222

On Thursday, January 12, 2012 9:02:35 am David Johnston wrote:

> ----------------------------------------
> 
> Adrian, you are not helping...if ON UPDATE CASCADE was enabled on "orders"
> the error in question would never have appeared and the UPDATE would have
> succeeded.  Carlos' goal is to change the value of a Primary Key that has
> already been used in a FOREIGN KEY constraint and he needs to learn to use
> the documentation to solve some of these basic questions instead of asking
> the list.   His approach is correct, execute UPDATE against the
> "developers" table.

My mistake, I got the table relationship order wrong. Sorry for the noise.

> 
> David J.

-- 
Adrian Klaver
adrian.klaver@gmail.com