You are making it harder by having the parent-child relationships in a text field. You have to read and parse the text field in order to figure out whom the parent or child is.

I suggest you try this as your table,

Table: Categories

id         (primary key)
parent_id  (foreign key on the id column, set to NULL for the upper-mo
+st node)
name       text

[download]

This simple structure will allow you to go infinite levels deep without an abitrary limits like your current tables (due to the size of your text columns).

As for the coding, you just need one recursive routine, to build your tree.

my $dbh = DBI::connect(@connect_values_here);
get_categories_at( undef );


sub get_categories_at {
  my $parent_id = shift;

  my @values;
  my $sql = "SELECT * FROM TABLE WHERE ";

  if (not defined $parent_id) {
     $sql .= "parent_id IS NULL";
  }
  else {
     $sql .= "parent_id = ?";
     push @values, $parent_id;
  }

  my $hash_ref = $dbh->selectall_hashref( $sql, 'id', {}, @values);

  for my $id (keys %{$hash_ref}) {
    print "ID => $id\n";
    get_categories_at( $hash_ref->{$id}{parent_id} );
  }
}

[download]

This has some short-comings, mainly I did not test it for one, and it does not print the categories in a particular order (though that can easily be fixed). This should be a good enough starting point to test your own model though.

Good Luck

In reply to Re: Pulling back paths from a database to populate form field by Herkum
in thread Pulling back paths from a database to populate form field by coldfingertips

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.