 | | 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)
|
