You will have to create a lot LESS perl code, if you use Class::DBI to define your tree structure. You could do something like this:
package TreeNode; use base 'Class::DBI'; __PACKAGE__->table('forrest'); __PACKAGE__->has_a(parent=>TreeNode); __PACKAGE__->has_many(children=>TreeNode);
Note that there are several ways of representing a tree structure inside a relational database:

Each of those representations has it's advantages and it's disadvantages, depending on what you intend to do with the tree once you have it in the database.

Whichever method you choose to implement, I am willing to bet the code will be much cleaner (more readable and easier to debug) if you use Class::DBI than if you use straight SQL in the code.


In reply to Re: (OT?) Recursive sql queries? by matija
in thread (OT?) Recursive sql queries? by BUU

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.