From: David Clarke <pigwin32@gmail.com>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-sql@postgresql.org
Subject: Re: Alternative to serial primary key
Date: Sat, 8 Jul 2006 08:52:22 +1200
Message-ID: <12b7ac1e0607071352x1b82c98bx3eb8047d693b4bc0@mail.gmail.com> (raw)
In-Reply-To: <20060707112113.GH26210@phlogiston.dyndns.org>
References: <bf05e51c0607060902vdd8d993u470c128abf127d3d@mail.gmail.com>
<20060706183920.46008.qmail@web33314.mail.mud.yahoo.com>
<12b7ac1e0607061330o34adbd6ds9bd624d3889c7fe7@mail.gmail.com>
<20060706171816.9f248316.darcy@druid.net>
<20060707112113.GH26210@phlogiston.dyndns.org>
On 7/7/06, Andrew Sullivan <ajs@crankycanuck.ca> wrote:
> On Thu, Jul 06, 2006 at 05:18:16PM -0400, D'Arcy J.M. Cain wrote:
> > owns/resides there in a situation where the address can never be
> > changed, e.g. "521 Main" splitting into "521A Main" and "521B Main."
>
> And anyone who has looked at an even moderately old city map will
> tell you that even this "impossible case" is by no means impossible.
>
Actually for my purposes it doesn't matter, I'm using a freeform
address string to index a lat/long. I fully expect to have multiple
unique addresses with a duplicate lat/long, i.e. the location doesn't
change - only the name of it. I'm personally hoping not to be around
long enough for geological events to change the physical location but
living in the shaky isles anything is possible.
Thanks again to all who have responded. I guess I'm probably labouring
the point but it's been instructive at least. Being fairly new to
database design I wanted to have enough info to be confident with my
approach.
Dave
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: pigwin32@gmail.com, ajs@crankycanuck.ca
Subject: Re: Alternative to serial primary key
In-Reply-To: <12b7ac1e0607071352x1b82c98bx3eb8047d693b4bc0@mail.gmail.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