Re: Primary Key

From: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Primary Key
Date: 2007-11-17 04:49:19
Message-ID: 473E72CF.6090806@cox.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/16/07 20:50, Greg Smith wrote:
[snip]
>
> He doesn't use that example anymore but still misses the point I tried
> to make. The ability of the world to invalidate the assumptions that go
> into natural key assignment are really impressive. I particularly enjoy
> that so many systems are built presuming that the Social Security number
> for a person is involatile that this topic comes up in their FAQ about
> identify theft: http://www.socialsecurity.gov/pubs/10064.html

Natural PKs are *not* set in stone, and only stubborn fools won't
admit that they can't divine all situations. So, you add a new
column to the PK and keep on going.

But still, there *are* some circumstances where natural PKs just
don't work. After all, SSNs and credit card numbers are synthetic
(just not generated sequential by the RDBMS).

- --
Ron Johnson, Jr.
Jefferson LA USA

%SYSTEM-F-FISH, my hovercraft is full of eels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHPnLPS9HxQb37XmcRAggNAKCL8UDTQ3238mbYIiV32AUAnOs+aQCgkhTP
yr+t6pT5loh7PBUc3QPljD4=
=O/Eb
-----END PGP SIGNATURE-----

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-11-17 05:36:35 Re: pg_dump not including custom CAST?
Previous Message Merlin Moncure 2007-11-17 04:16:17 Re: Primary Key