Subject:
|
Re: Another heirarchical DB question
|
Newsgroups:
|
lugnet.off-topic.geek
|
Date:
|
Mon, 20 Nov 2000 18:13:56 GMT
|
Viewed:
|
1266 times
|
| |
|
|
In lugnet.off-topic.geek, Jim Hughes wrote:
> Hi:
>
> First thanks to Christopher, Steve and Larry for your help with my last
> question.
Really? All that mumbo-jumbo helped? We'll have to try harder this time.
> Here's todays question. Say that you had a list of data that needed to be not
> only in heirarchical order but also each child of a given parent needed to
> be in a specific order, e.g:
>
> -- Technic
> ---- Cross Axles
> ------ Cross axle, 2L
> ------ cross axle, 3L
> ------ cross axle, 4L
> ------ cross axle, 5L
>
> all of the specific cross axles are parents of the cross axle category so
Generally speaking, the specific cross-axles would be described as children
of the Cross Axles category. And the Cross-Axles category would be a child
of the Technic category.
> how can
> I assure that the DB will 'know' that they are related in a specific order, in
> this case length.
Relate each cross-axle *directly* to the Cross Axle category, not to each
other.
If the data can't be sorted by name, add a column specifically for sorting.
Steve
|
|
Message is in Reply To:
 | | Another heirarchical DB question
|
| Hi: First thanks to Christopher, Steve and Larry for your help with my last question. Here's todays question. Say that you had a list of data that needed to be not only in heirarchical order but also each child of a given parent needed to be in a (...) (26 years ago, 20-Nov-00, to lugnet.off-topic.geek)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
