The design doesn't have to be fancy.. but it does have to be correct. Organizing the data in a normalized way will make it faster, easier to implement, and MUCH easier to extend later.
Always think ahead... *especially* when you are dealing with people in sales. :) Out of 10 projects developed for sales purposes, all 10 of them will want extra functionality after the project is completed. I absolutely guarantee it (or your money back). hehehe
Update: Thought I'd clarify on the "easier to implement" bit. Okay, you'll have to do an extra lookup to match a few keys to their values -- like matching the
make_id to the
make text string. But, when it comes time to write search code, it's faster and easier to develop a search that does a numerical match, rather than some kind of regexp match on the string!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.