Subject:
|
Re: Online LEGO Inventory Database
|
Newsgroups:
|
lugnet.db.brictionary
|
Date:
|
Thu, 10 Feb 2000 19:48:42 GMT
|
Viewed:
|
8420 times
|
| |
|
|
Steve Bliss wrote in message ...
> In lugnet.db.brictionary, Steve Hodge wrote:
>
> > In lugnet.db.brictionary, Steve Bliss writes:
>
> > > Yep. A better approach may be modeling a set of properties. So a plate • with
> > > holes in it could have both the Technic and Plate properties. This would • avoid
> > > requiring a hierarchical classification (is that redundant?) system.
> >
> > Yeah, I agree. One of the other threads had come to the same conclusion • and
> > are curently trying to decide exactly which properties would be necessary.
>
> Having a good list of properties at the start is a good idea, but don't
> hard-code specific properties into the schema. It's just a many-to-many
> relation between parts and properties. Assuming a relational approach.
It will be a relational database, and I tend to remove all hard codings
possible.
I will be designing the schema later today, and posting it for everyone to
rip apart =)
--Eric
|
|
Message is in Reply To:
 | | Re: Online LEGO Inventory Database
|
| (...) Having a good list of properties at the start is a good idea, but don't hard-code specific properties into the schema. It's just a many-to-many relation between parts and properties. Assuming a relational approach. Steve (27 years ago, 10-Feb-00, to lugnet.db.brictionary)
|
9 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
