Birthdates can change. Do your users never make typo's when entering data?

-----Original Message-----
From: Justin Taylor [mailto:JUSTIN@xxxxxxxxxxxxx]
Sent: Monday, August 28, 2017 12:40 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Database design question

Why would you ever willingly choose not to have a primary key?

-----Original Message-----
From: Raul Jager [mailto:raul@xxxxxxxxxx]
Sent: Monday, August 28, 2017 12:33 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Database design question

A primary key is a good idea, but not really necessary. If you have a field, or group of fields that are unique, and that are very unlikely to change (like birth date) you can use as primary key.  DB2  handles very well a primary key that has several fields, so you can use it.  Some other databases will only work well with a single field as primary key, and even will require correlative numbers.

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support by shopping at with our affiliate link:

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].