Re: Alternative to serial primary key

From: "David Clarke" <pigwin32(at)gmail(dot)com>
To: "Andrew Sullivan" <ajs(at)crankycanuck(dot)ca>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Alternative to serial primary key
Date: 2006-07-06 11:32:36
Message-ID: 12b7ac1e0607060432i5fd3aa4ap16af10b9efabb917@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On 7/6/06, Andrew Sullivan <ajs(at)crankycanuck(dot)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.

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Chris Browne 2006-07-06 12:28:44 Re: Alternative to serial primary key
Previous Message Markus Schaber 2006-07-06 11:28:58 Re: Alternative to serial primary key