joealba made the valuable suggestion that you "normalize" your data. If you are not a DB guru this may not mean much. Here is a paper describing the concepts in a fairly readable way. The link takes you into the middle of an article, starting with a section "Why Normalize". You may want to go back to the beginning if you are not familiar with the definitions. There are lots of good articles on the web, but this may help get you started on why and how to normalize. There is also a good collection of info on About. I found the normalization series exceptionally clear.
Regardless of the tool you use, normalization does help. In general, database practice is pretty well evolved. Some techniques may seem like overkill (and some may be), but they may make your overall design and programming task easier.
HTH, --traveler
-
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.
|
