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