comment on

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.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re: Unlimited groups/categories by BrowserUk
in thread Unlimited groups/categories by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Think about Loose Coupling
	PerlMonks