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!
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|