From: Richard Huxton <dev@archonet.com>
To: beyaRecords - The home Urban music <uzo@beya-records.com>
To: pgsql-sql@postgresql.org
Subject: Re: Mechanics of Update:Cascade
Date: Sat, 31 Jan 2004 17:42:00 +0000
Message-ID: <200401311742.00784.dev@archonet.com> (raw)
In-Reply-To: <3968B922-53DB-11D8-A6EB-0003938366A4@beya-records.com>
References: <3968B922-53DB-11D8-A6EB-0003938366A4@beya-records.com>
On Saturday 31 January 2004 10:50, beyaRecords - The home Urban music wrote:
> Hi,
> could someone please explain to me the mechanics of an UpDate:Cascade?
> Delete:Cascade I fully understand but not Update. I have 2 tables A and
> B. On B I have created a foreign key on user_id in both B and A for
> Update and Delete cascade. If I delete from A it deletes all from B. If
> I update A what happens in B?
The column should be changed there too. For example, if we have
B.user_id => A.user_id and change A.user_id from 100 to 200 then the same
should happen in B too.
--
Richard Huxton
Archonet Ltd
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: dev@archonet.com, uzo@beya-records.com
Subject: Re: Mechanics of Update:Cascade
In-Reply-To: <200401311742.00784.dev@archonet.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