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: Thu, 6 Jul 2006 23:32:36 +1200
Message-ID: <12b7ac1e0607060432i5fd3aa4ap16af10b9efabb917@mail.gmail.com> (raw)
In-Reply-To: <20060706111223.GC26210@phlogiston.dyndns.org>
References: <12b7ac1e0607060316ub7b5e21i5e8e3bef2504e02c@mail.gmail.com>
<44ACEA1C.9030804@logix-tt.com>
<12b7ac1e0607060406r16d03f74mfa303eec9ab4821f@mail.gmail.com>
<44ACEFBF.7030903@logix-tt.com>
<20060706111223.GC26210@phlogiston.dyndns.org>
On 7/6/06, Andrew Sullivan <ajs@crankycanuck.ca> wrote:
> That sort of undermines the value of the calculated primary key,
> though, doesn't it? He'd need the unique index for FK references,
> which was the point, I thought.
>
Yes, that occurred to me as well. Frankly I believe the md5 collision
generation is more of a practical issue for crypto where for my
purposes the potential for two residential street addresses to
generate the same md5 hash value is effectively zero. And the md5
function is a builtin which I would hope is faster than anything I
could write in pgsql. Could be wrong, I have been before.
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: <12b7ac1e0607060432i5fd3aa4ap16af10b9efabb917@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