×
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.
. Every table should have a primary key. The Primary Key should be
an identity column, NOT business data
In regard to having a primary key, that comes right from Codd's 12 rules
for a RDBMS.
In regard to an identity column (the DBMS auto increments the value), that
may be fine for some tables, overkill for others. I definitely have a warm
spot in my heart for surrogate keys, which facilitate logical joins and
referential integrity; my preference is to generate them in database event
handlers (behind triggers) rather than in application code.
In regard to "NOT business data", what about code files (e.g. state codes)?
. Create business key as unique from business data, not Primary Key
Fine, if the primary key fails to meet all application requirements, which
is often the case.
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
