pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Karsten Hilbert <Karsten.Hilbert@gmx.net>
To: pgsql-sql@postgresql.org
Subject: Re: surrogate key or not?
Date: Sat, 24 Jul 2004 11:06:35 +0200
Message-ID: <20040724110634.B699@hermes.hilbert.loc> (raw)
In-Reply-To: <19813.1090591668@sss.pgh.pa.us>
References: <1090325769.3241.27.camel@dicaprio.akademie1.de>
	<200407221005.59482.josh@agliodbs.com>
	<20040723085721.C728@hermes.hilbert.loc>
	<0407231327461F.01150@thenilgiris.com>
	<FF7F62AC-DC8E-11D8-AA48-000A95C88220@myrealbox.com>
	<19813.1090591668@sss.pgh.pa.us>

On Fri, Jul 23, 2004 at 10:07:48AM -0400, Tom Lane wrote:

> The other standard reason for using a made-up value as primary key is
> that it's under your control and you can guarantee it isn't going to
> change: one record will have the same primary key for its entire life,
> which vastly simplifies handling of foreign keys and so forth.
That is pretty much the main reason why our schema does so.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

view thread (44+ messages)  latest in thread

Message-ID: <20040724110634.B699@hermes.hilbert.loc>
Permalink:  ../20040724110634.B699@hermes.hilbert.loc/
Also on:    postgresql.org/message-id/20040724110634.B699@hermes.hilbert.loc

copy link · copy postgr.es

reply

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: Karsten.Hilbert@gmx.net
  Subject: Re: surrogate key or not?
  In-Reply-To: <20040724110634.B699@hermes.hilbert.loc>

* 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