From: Karsten.Hilbert@gmx.net
To: pgsql-sql@postgresql.org
Subject: Re: surrogate key or not?
Date: Fri, 23 Jul 2004 22:36:23 +0200
Message-ID: <20040723223623.A612@hermes.hilbert.loc> (raw)
In-Reply-To: <200407231017.11605.josh@agliodbs.com>
References: <Pine.LNX.4.44.0407231453090.15184-100000@matrix.gatewaynet.com>
<200407231017.11605.josh@agliodbs.com>
Josh,
> > 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.
thanks so much - this is exactly the kind of assurance I was
looking for.
BTW, I will come back to your generous offer in August.
Thanks again.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
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: <20040723223623.A612@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