Subject:
|
Re: wishing upon a star
|
Newsgroups:
|
lugnet.db.brictionary
|
Date:
|
Wed, 25 Aug 1999 20:46:08 GMT
|
Viewed:
|
1851 times
|
| |
|
|
Larry Pieniazek wrote:
>
> Yes, indeed, John is (as evah) right. Let me weigh in here as well...
>
> Putting meaning in keys is a sign of not very well seasoned designers,
> IMHO.
>
> A pretty strong principle of database design is NOT to let your key have
> business meaning. Get keys from a source that is intended to be unique,
> then never ever ascribe meaning to them. All meaning should be in
> attributes.
Taking that to the ultimate suggests even the TLG part number should not
be the key (which of course is already a known issue if you want to
account for color and/or printing).
--
Frank Filz
-----------------------------
Work: mailto:ffilz@us.ibm.com
Home: mailto:ffilz@mindspring.com
|
|
Message has 1 Reply:
 | | Re: wishing upon a star
|
| (...) Precisely. It's not guaranteed to be unique and it has business meaning. Now, clearly, the underlying DB implementation should index on that column because we are likely to be doing a lot of lookups, but that is an optimization/implementation (...) (25 years ago, 25-Aug-99, to lugnet.db.brictionary)
|
Message is in Reply To:
| | Re: wishing upon a star
|
| Yes, indeed, John is (as evah) right. Let me weigh in here as well... Putting meaning in keys is a sign of not very well seasoned designers, IMHO. A pretty strong principle of database design is NOT to let your key have business meaning. Get keys (...) (25 years ago, 25-Aug-99, to lugnet.db.brictionary)
|
22 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
