RE: Database design question -- MIDRANGE-L

Subject: RE: Database design question
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Mon, 28 Aug 2017 16:40:12 +0000
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

The arbitrary identify column protects you in the case the business data key needs to change. In your example, if the customer numbers needs to change, it would be a non-issue if you have an identify column. If the customer number is the primary key, things get sticky.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Database design question , Rob Berendt
RE: Database design question , Rob Berendt

This mailing list archive is Copyright 1997-2025 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.