Each recursive call to walktree uses the same $children statement handle. So most likely, each time a recursive call re-executes the $children statement, it clobbers whatever was pending for the caller in that statement handle. When the control returns to the caller, there is nothing left to iterate over.

If you think about how things happen sequentially, walktree only returns once $children->fetchrow fails. Then right after it returns, the first thing the caller tries to do is $children->fetchrow!

To fix this, either make new statement handles within each call to walktree, or else fetch all of the results from the $children query into an array before recursing at all.

blokhead

In reply to Re: walking a tree by blokhead
in thread walking a tree by punkish

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.