From: David Clarke <pigwin32@gmail.com>
To: D'Arcy J.M. Cain <darcy@druid.net>
Cc: operationsengineer1@yahoo.com
Cc: postgresql@aranya.com
Cc: pgsql-sql@postgresql.org
Subject: Re: Alternative to serial primary key
Date: Fri, 7 Jul 2006 19:37:15 +1200
Message-ID: <12b7ac1e0607070037p4c2a94d4r8e6758be7b08ca95@mail.gmail.com> (raw)
In-Reply-To: <20060706171816.9f248316.darcy@druid.net>
References: <bf05e51c0607060902vdd8d993u470c128abf127d3d@mail.gmail.com>
<20060706183920.46008.qmail@web33314.mail.mud.yahoo.com>
<12b7ac1e0607061330o34adbd6ds9bd624d3889c7fe7@mail.gmail.com>
<20060706171816.9f248316.darcy@druid.net>
On 7/7/06, D'Arcy J.M. Cain <darcy@druid.net> wrote:
> Are you sure? I have a hard time imagining a situation where that
Absolutely.
> Also, you need to get into a lot more coding to handle the fact that
> "521 Main Avenue" is the same address as "521 Main Av." and "521 Main
> Ave" and even "521 Main."
Actually that is being done for me and you're correct, it is a lot of
effort but there are a variety of services out there and I'm not
trying to reinvent the wheel.
> And even given all of that, I would probably still use serial.
Because?
> Danger, Will Robinson. The phrase "regenerate my primary key"
> immediately raises the hairs on the back of my neck. If the primary
> key can ever change, you have a broken schema.
Perhaps my choice of words was somewhat hasty. A serial is totally
divorced from the data it represents whereas a md5 hash is (for my
purposes) unique, stable, verifiable, and simple.
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, darcy@druid.net, operationsengineer1@yahoo.com, postgresql@aranya.com
Subject: Re: Alternative to serial primary key
In-Reply-To: <12b7ac1e0607070037p4c2a94d4r8e6758be7b08ca95@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