 | | Re: Online LEGO Inventory Database —Eric Vitiello
|
| | | (...) I (...) to (...) Perhaps (...) be (...) Sounds good to me! I'm going to begin by designing the database to hold the data, and deciding on the best method to catalog the parts, or the best existing database to use for the parts. Any suggestions (...) (25 years ago, 7-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
| | | |
| | | | | Re: Online LEGO Inventory Database —Steve Hodge
|
| | | | (...) One problem we have at the moment is that the various sources of parts lists (LDraw, Tim Vattima's set inventories, Auczilla, Technica, etc) all contain different subsets of the full parts list and use different descriptions. We need to (...) (25 years ago, 7-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
| | | | |
| | | | | | Re: Online LEGO Inventory Database —Steve Bliss
|
| | | | (...) 'The database' should allow multiple descriptions per piece. And should have the major descriptions pre-loaded. The core element table should have an abstract key value, and a pointer to a graphic image for each part. A second table, call it (...) (25 years ago, 7-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
| | | | |
| | | | | | Re: Online LEGO Inventory Database —Steve Hodge
|
| | | | (...) collate. (...) Yep. The difficulty is in matching up the descriptions from the various sources (e.g. which LDraw part is this Technica part?). Sometimes it's easy, somethimes it's not. (...) Yep. (...) part (...) a (...) and (...) That's the (...) (25 years ago, 9-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
| | | | |
| | | | | | Re: Online LEGO Inventory Database —Steve Bliss
|
| | | | (...) Yep. (...) Oh, and each description should probably be tagged with a source. That way, when we change the description of some part in LDraw, the cross-reference database can be updated. (...) Yep. A better approach may be modeling a set of (...) (25 years ago, 9-Feb-00, to lugnet.db.brictionary)
|
| | | | |
| | | | | | Re: Online LEGO Inventory Database —Steve Hodge
|
| | | | (...) have (...) I'd thought about this earlier, but forgot to mention it. (...) based (...) Once (...) avoid (...) Yeah, I agree. One of the other threads had come to the same conclusion and are curently trying to decide exactly which properties (...) (25 years ago, 10-Feb-00, to lugnet.db.brictionary)
|
| | | | |
| | | | | | Re: Online LEGO Inventory Database —Steve Bliss
|
| | | | (...) 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 (25 years ago, 10-Feb-00, to lugnet.db.brictionary)
|
| | | | |
| | | | | | Re: Online LEGO Inventory Database —Eric Vitiello
|
| | | | | Steve Bliss wrote in message ... (...) with (...) and (...) 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 (25 years ago, 10-Feb-00, to lugnet.db.brictionary)
|
| | | | | |
| | | | | | Re: Online LEGO Inventory Database —Eric Vitiello
|
| | | | Steve Bliss wrote in message ... (...) with (...) and (...) Here is the current scema. I have decided to concentrate on the parts section, and themn move onto creating a set inventory section (which I think will be the easy part)... Total of 6 (...) (25 years ago, 10-Feb-00, to lugnet.db.brictionary)
|
| | | | |
