Better would be to have the root message and all its replies share a single value (e.g., root_msg_id) on which you have built an index.

Then you only need one select to pull them all in. You will still need to sort out the hierarchical relationships, but you've got parent_id, level_id, etc. in the table already.

Any benchmarking you do will indicate that one sql select is as slow as executing several hundred (if not thousand) lines of procedural code. The slight amount of thrashing in perl to sort things is more than made up for by eliminating all but the one select.

In reply to Re: Message Board Threading with DBI/MySQL by voyager
in thread Message Board Threading with DBI/MySQL by Red Neckerson

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.