Hierarchal data, and relational DBs do not mix well. There are hackish solutions involving adjacency lists and several variations, but they are all inefficient and clumsy at best, and downright friggin' awkward at worst.
See MySQL:Managing hierachal data for the skinny.
It gets easier with Stored Procedures, but it can still get slow and messy. Sometimes, it is worth at least asking the question: is there a better way to persist my data than a RDBMS, and hierarchal data is one such time.
The primary questions are:
- Do you need concurrancy?
- Do you need performance?
- What volumes are you dealing with?
A realistic take on the answers to those questions can go a long way to suggesting other possible alternatives.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.