×
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.
In my case, I would make that architecture decision based on
requirements.
Same here. I've been using more sequential, numeric identity keys lately, but Rob had a good point about the State Code table. The state code is a lot more descriptive than a numeric identifier, and easier to remember for data entry, and very unlikely to change.
Consistency is a consideration but not an overriding
one.
I agree.
The trick is deciding when they are appropriate, and that
can be different for different circumstances.
One question I ask myself is whether there might be any cause to allow users to change an otherwise descriptive key field in a maintenance program. Maybe it's a data warehouse used for reporting where rules of normalization may not strictly apply. If so, then use an identity key rather than a descriptive one.
-Nathan.
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
