X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0568B14B2880 for ; Sun, 8 Aug 2004 22:32:29 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 14627-08 for ; Mon, 9 Aug 2004 01:32:23 +0000 (GMT) Received: from www.postgresql.com (www.postgresql.com [200.46.204.209]) by svr1.postgresql.org (Postfix) with ESMTP id B7CC614B28B6 for ; Sun, 8 Aug 2004 22:32:01 -0300 (ADT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by www.postgresql.com (Postfix) with ESMTP id CBEC55A24CA for ; Sun, 8 Aug 2004 19:18:56 -0300 (ADT) Received: from [64.81.245.111] (HELO temoku.sf.agliodbs.com) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6027405; Sun, 08 Aug 2004 15:20:12 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Kenneth Gonsalves , Oliver Elphick Subject: Re: surrogate key or not? Date: Sun, 8 Aug 2004 15:19:16 -0700 User-Agent: KMail/1.5.4 Cc: pgsql-sql@postgresql.org References: <1090325769.3241.27.camel@dicaprio.akademie1.de> <1091927196.13140.174.camel@linda> <0408080559370M.01190@thenilgiris.com> In-Reply-To: <0408080559370M.01190@thenilgiris.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200408081519.16162.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/56 X-Sequence-Number: 18553 Kenneth, > but why would anyone want to change the value of an autogenerated serial row? But if you're using a real key, it may need to change. The only reason *not* do do it that way is performance issues with CASCADE. -- -Josh Berkus Aglio Database Solutions San Francisco