From: Josh Berkus <josh@agliodbs.com>
To: Achilleus Mantzios <achill@matrix.gatewaynet.com>
To: Kenneth Gonsalves <lawgon@thenilgiris.com>
Cc: Michael Glaesemann <grzm@myrealbox.com>
Cc: Karsten Hilbert <Karsten.Hilbert@gmx.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: surrogate key or not?
Date: Fri, 23 Jul 2004 10:17:11 -0700
Message-ID: <200407231017.11605.josh@agliodbs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0407231453090.15184-100000@matrix.gatewaynet.com>
References: <Pine.LNX.4.44.0407231453090.15184-100000@matrix.gatewaynet.com>
Achilleus,
> In other words, with surrogate keys, you eliminate the chance
> that your original design was flawed due to lack of important
> initial knowledge.
Well, you don't *eliminate* it, but you do decrease it.
I'd say, yes, this is an important 4th reason:
4) Your spec may be incorrect and surrogate keys make it easier to make design
changes in production.
Once again, though, this is an *implementation* issue and not a *logic* issue,
as I asserted ...
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, achill@matrix.gatewaynet.com, lawgon@thenilgiris.com, grzm@myrealbox.com, Karsten.Hilbert@gmx.net
Subject: Re: surrogate key or not?
In-Reply-To: <200407231017.11605.josh@agliodbs.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