×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
