To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.db.brictionaryOpen lugnet.db.brictionary in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Database / Brictionary / 29
    Re: wishing upon a star —Robert Munafo
   (...) 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: wishing upon a star —Adam Howard
   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 —John Cromer
   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 —Larry Pieniazek
   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 —Frank Filz
     (...) 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 —Larry Pieniazek
     (...) 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 —Steve Bliss
     (...) 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 —Tamyra Teed
     (...) 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)
    
         Re: wishing upon a star —Robert Munafo
     (...) It sounds like you're talking about the mold quality control numbers. On most LEGO parts that a large enough concealed surface, you find three numbers -- two vary from part to part for the reasons you describe. These are usually one or two (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
   
        Re: wishing upon a star —Dave Lovelace
   (...) 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 —Larry Pieniazek
     (...) 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)
    
         OID generation (was: Re: wishing upon a star) —Todd Lehman
     (...) 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: OID generation (was: Re: wishing upon a star) —Larry Pieniazek
      (...) 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: OID generation (was: Re: wishing upon a star) —Robert Munafo
     (...) Just to save others the effort -- "wolog" occurs 3 times on Hotbot and 28 times in Alta Vista. The best interpretation in this context appears to be an abbreviation for "without loss of generality". - Robert Munafo (URL) LEGO: TC+++(8480) SW++ (...) (25 years ago, 26-Aug-99, to lugnet.off-topic.geek)
    
         Re: OID generation (was: Re: wishing upon a star) —Larry Pieniazek
     (...) If you didn't already know that.... you have to ask yourself... do you feel lucky? huh, do ya? ... <slap> whoops. wrong thread. you have to ask yourself, are you geeky enough to be on this group? <grins, ducks and runs> (25 years ago, 26-Aug-99, to lugnet.off-topic.geek)
    
         Re: OID generation (was: Re: wishing upon a star) —Chris Moseley
      Larry Pieniazek <lar@voyager.net> wrote (...) Come on Larry, even *I* had to check hotbot to find that out. And I thought it was only 27 times on Alta Vista. Moz (25 years ago, 28-Aug-99, to lugnet.off-topic.geek)
   
        Re: wishing upon a star —John Cromer
   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 —Dave Lovelace
   (...) Thank you for the kind words, John...and the insights. I am a two-month old "newbie" and have very little to offer gods of thinking such as yourself, and also of course the other geniuses involved in this discussion, other than simple hero (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
   
        Re: wishing upon a star —Robert Munafo
     (...) Not so fast, my humble friend... Just because it isn't used as the database key or as the "unique definitive" part number doesn't mean your part numbers have no merit. I supported your suggestion because I felt it was appropriate to include a (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
   
        Re: wishing upon a star —John Cromer
   In lugnet.db.brictionary, Dave Lovelace writes: [SNIP] (...) ...you are all truly brilliant, and obviously experienced, (...) Please don't let Lar here this! His head is quite large enough already.... :^) as evah, John C. (25 years ago, 27-Aug-99, to lugnet.db.brictionary)
   
        Re: wishing upon a star —Larry Pieniazek
   (...) c /here/hear/ ... but who's here to notice? (...) Swelled heads typically occur when new facts are uttered. Nothing was by Dave that I didn't already know to be true about myself so there's no danger of (additional) swelling. But seriously, I (...) (25 years ago, 27-Aug-99, to lugnet.db.brictionary)
   
        Re: wishing upon a star —Dave Lovelace
    (...) Har! No, really...you brains good and my bad and me grammar good too! I got exactly what I wanted...a flurry of responses, in a simple endeavor to find out if the best and brightest have come up with any solutions to a part search and (...) (25 years ago, 27-Aug-99, to lugnet.db.brictionary)
 

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR