Subject: Re: surrogate key or not?
From: Oliver Elphick <olly@lfix.co.uk>
Reply-To: olly@lfix.co.uk
To: Kenneth Gonsalves <lawgon@thenilgiris.com>
Cc: pgsql-sql@postgresql.org
In-Reply-To: <0408070930300J.01190@thenilgiris.com>
References: <1090325769.3241.27.camel@dicaprio.akademie1.de>
	<41026D55.3040002@zara.6.isreserved.com>
	<200408061542.04336.josh@agliodbs.com>
	<0408070930300J.01190@thenilgiris.com>
Content-Type: text/plain
Organization: LFIX Limited
Message-Id: <1091927196.13140.174.camel@linda>
Mime-Version: 1.0
Date: Sun, 08 Aug 2004 02:06:36 +0100
Content-Transfer-Encoding: 7bit

On Sat, 2004-08-07 at 05:00, Kenneth Gonsalves wrote:
> why shouldnt the primary key change? the only key that should never change is 
> a key that is used as a foreign key in another table. In a table like this:
> 
> id serial unique
> name varchar primary key
> 
> name may change - id will never change. id is used as the foreign key

It can change if you use ON UPDATE CASCADE in the foreign key
definitions.

-- 
Oliver Elphick                                          olly@lfix.co.uk
Isle of Wight                              http://www.lfix.co.uk/oliver
GPG: 1024D/A54310EA  92C8 39E7 280E 3631 3F0E  1EC0 5664 7A2F A543 10EA
                 ========================================
     "Be still before the LORD and wait patiently for him;
      do not fret when men succeed in their ways, when they
      carry out their wicked schemes." 
                            Psalms 37:7