From: Adrian Klaver <adrian.klaver@gmail.com>
To: David Johnston <polobo@yahoo.com>
Cc: pgsql-sql@postgresql.org, "'Carlos Mennens'" <carlos.mennens@gmail.com>
Subject: Re: Unable To Modify Table
Date: Thu, 12 Jan 2012 09:10:02 -0800
Message-ID: <201201120910.02794.adrian.klaver@gmail.com> (raw)
In-Reply-To: <017101ccd14b$fbc0f120$f342d360$@yahoo.com>
References: <CAAQLLO70j_j-nz7sZmXbcKT7QRmuf6oQRsCT_N5=+8UC7NFp1A@mail.gmail.com>
<201201120854.42306.adrian.klaver@gmail.com>
<017101ccd14b$fbc0f120$f342d360$@yahoo.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: adrian.klaver@gmail.com, polobo@yahoo.com, carlos.mennens@gmail.com
Subject: Re: Unable To Modify Table
In-Reply-To: <201201120910.02794.adrian.klaver@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox