| | RE: wishing upon a star
|
|
Let me add my support to this as well. Make the key be some arbitrary unique number. I've been programming for about 17-18 years, and in the early days I would have disagreed. Experience has proven otherwise. --- Dave Hylands Email: (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
|
|
| | Re: OID generation (was: Re: wishing upon a star)
|
|
(...) Quick answer: yes. Long answer: Almost certainly. There are some tradeoffs that you've made. A big one is around the human readability of the key. Ask yourself, how often do humans inspect these, and how fast can you convert back to 40bit (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary, lugnet.off-topic.geek)
|
|
| | Re: wishing upon a star
|
|
(...) For anyone that might not know this, Mold numbers are not unique. A mold is setup for all the parts and it makes more than 1 piece at a time. If you take the 2x4 brick mold, it could possibly do 8 bricks at a time which means each brick in the (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
|
|
| | OID generation (was: Re: wishing upon a star)
|
|
(...) Lar, I've been experimenting with a method for OID construction which takes a pseudorandom 32-bit integer, converts it to a 40-bit integer by adding 8 bits of CRC, then converts that an to 8-byte base-32 ASCII representation using the 32 (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary, lugnet.off-topic.geek)
|
|
| | Re: wishing upon a star
|
|
(...) It's known to be not unique, there's a many-to-many relationship between TLG numbers and unique mold-forms. That is, the same number has been used for different parts (at least, different versions of parts), and different numbers have been (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
|
|
| | Re: wishing upon a star
|
|
(...) Whoops. Talking in shorthand tripped me up. In system-architect-speak "business" logic is the actual desired work effort of the program (contrasted with non business logic which is the infrastructure or other code that you have to do in order (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary, lugnet.off-topic.geek)
|
|
| | Re: wishing upon a star
|
|
In lugnet.db.brictionary, Dave Lovelace writes: [SNIP] (...) Well, not so fast. All ideas are welcome here. Maybe a larger perspective might help. I understand the frustration of an ignoramus coming to LEGO parts naming and numbering. I've been (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
|
|
| | Re: wishing upon a star
|
|
(...) Pardon my inexperience. I am neither a program designer, nor a person with any business logic whatsoever...perhaps I should have footnoted these factss before sticking my idea out here. I think that 90% of the users of a would-be (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
|
|
| | 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)
|
|
| | Re: wishing upon a star
|
|
(...) 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). (25 years ago, 25-Aug-99, to lugnet.db.brictionary)
|
|
| | 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)
|
|
| | Re: wishing upon a star
|
|
Hi guys, I would urge caution on the creation of complex codes to identify pieces. I admit, I am prejudiced. I worked on a database management project back in the early 80s for a water-quality study in which water samples were identified with a (...) (25 years ago, 25-Aug-99, to lugnet.db.brictionary)
|
|
| | Re: wishing upon a star
|
|
Hi Dave & Robert, Robert Munafo <munafo@gcctechNO.SPAMcom> wrote in message news:FGzv17.4G8@lugnet.com... (...) bricks. (...) the (...) one of (...) I like this idea. I think we could use the rest of the digits to identify the piece more accurately. (...) (25 years ago, 25-Aug-99, to lugnet.db.brictionary)
|
|
| | Re: wishing upon a star
|
|
(...) I like this system, but just want to comment that it's not a complete substitute for the part numbers that LEGO molds on the bottom of the bricks. Another issue is that there are an awful lot of parts that don't fall into the category of (...) (25 years ago, 25-Aug-99, to lugnet.db.brictionary)
|
|
| | Re: Part 4180
|
|
(...) Yes. :-) It first came with train wheels (it's situated with the train elements) -- 1980; both 2x2 and 3x3, but later (1981?), studded hubs were added. One of many discrepancies the Numbers Group has mentioned to Terry, but which have yet to (...) (25 years ago, 22-Aug-99, to lugnet.db.brictionary)
|
|
| | Part 4180
|
|
I have a part 4180, but it has car wheels, not train wheels. Isn't part 4180 just the holder? /Tore (25 years ago, 21-Aug-99, to lugnet.db.brictionary)
|
|
| | Re: Question from a newbie
|
|
Hi Craig, The following 3 sites might help you. They give part names, images and (in some cases) numbers: (URL) (for Technic only) (2 URLs) C. In lugnet.db.brictionary, Craig Livingston writes: [SNIP] (...) (25 years ago, 18-Aug-99, to lugnet.db.brictionary)
|
|
| | Re: Question from a newbie
|
|
Hi Craig, Welcome and thanks for posting! Craig Livingston <CLivin007@aol.com> wrote in message news:FGL6HI.JpL@lugnet.com... (...) legos. (...) the (...) and (...) brick-naming (...) nomenclature (...) Yes you did come to the right place (I think (...) (25 years ago, 17-Aug-99, to lugnet.db.brictionary)
|
|
| | Question from a newbie
|
|
I really don't know if this is right place to post this, but here goes: Since coming out of my own dark ages, I have really gotten involved in legos. I enjoy reading lugnet.com's newsgroups, but often I am unable to decipher the meaning of a brick (...) (25 years ago, 17-Aug-99, to lugnet.db.brictionary)
|
|
| | Re: brictionary request
|
|
(...) Probably not -- unless the output format just happens to work with your program. When a real database of parts does get off the ground (with the ability for people to contribute directly to it in an automated way), I'm almost certain that you (...) (25 years ago, 12-Aug-99, to lugnet.db.brictionary)
|