Subject:
|
Re: A heirarchical database question
|
Newsgroups:
|
lugnet.off-topic.geek
|
Date:
|
Fri, 17 Nov 2000 16:42:00 GMT
|
Viewed:
|
166 times
|
| |
|
|
In lugnet.off-topic.geek, Larry Pieniazek wrote:
> (I don't like redundancy in database designs, it causes data staleness and
> introduces errors)
Agreed. But sometimes, the price paid for normalization is too high. It
depends on the level of adhoc querying against the data. And the skill
level of the developer.
Steve
|
|
Message has 1 Reply:
 | | Re: A heirarchical database question
|
| (...) Agreed. But the original design was broken. I proposed two alternatives, both less redundant and both "more correct", although flaws could be found in either one by the determined examiner. ++Lar (24 years ago, 18-Nov-00, to lugnet.off-topic.geek)
|
Message is in Reply To:
| | Re: A heirarchical database question
|
| In lugnet.off-topic.geek, Jim Hughes writes: would be the best way to describe it in a DB table? Would this work OK: (...) You don't want to use both parent and (grand) child in the same table. It won't work, or it will introduce unneeded (...) (24 years ago, 16-Nov-00, to lugnet.off-topic.geek)
|
6 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
|
|
|
|
