You got good advice from ikegami already. I just want to add, since we're OT, that I find this naming convention- 

CREATE TABLE `posts` (
    `post_id` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY,
    `post_cat` INT(11) UNSIGNED NOT NULL,
...

[download]

-completely annoying. It's like naming a hash like so %hash_variable_name. Redundant information is almost always suboptimal if not an outright mistake in code design. I have no idea how it's become popular in schema design. I'd rather see cat spelled out category or catalog or catamaran or whatever you're assuming everyone will know it's short for than see something like posts.post_cat.

In reply to Re: [OT] Database Design by Your Mother
in thread [OT] Database Design by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.