Re: integer id columns for all tables

From: Bob Badour <bbadour_at_pei.sympatico.ca>
Date: Fri, 25 Aug 2006 15:12:22 GMT
Message-ID: <qrEHg.1371$9u.21036@ursa-nb00s0.nbnet.nb.ca>

garhone wrote:

> Hi,
>
> Someone with greater expertise than I recently told me that it is best
> to have an integer primary-key for all tables in a database, even if
> the table already has some non-integer primary key, or some sort of
> composite primary key. If there is already a non-integer key, then
> create a new sequence column and set that as the primary key.
>
> Does anyone have an opinion on this and why?

He sounds like an idiot who learned a simplistic rule that relieves him from having to think.

The design criteria for candidate keys are: simplicity, stability, familiarity and irreducibility. While an arbitrary id column is simple, stable and irreducible, it is not familiar and will not in any way keep your staff from duplicating entries.

I highly recommend Fabian Pascal's _Practical Issues in Database Management_ book. Received on Fri Aug 25 2006 - 10:12:22 CDT