It needs to go an arbitrary number of levels, right now it's limited to a
parent and a child level (because of the single JOIN). You can extend that
algorithm by adding additional JOIN clauses, but that's not a solution,
because it requires you to know how deep the maximum nesting is when you're
w
table to
itself for purposes of sorting heirarchical information.
M
-Original Message-
From: Barney Boisvert [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2003 12:55 PM
To: CF-Talk
Subject: RE: MySQL Heirarchies (fwd)
It needs to go an arbitrary number of levels, righ
s.postgresql.org/pgsql-general/2000-06/msg00449.php
- Original Message -
From: "Haggerty, Mike" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Tuesday, October 21, 2003 4:04 PM
Subject: RE: MySQL Heirarchies (fwd)
> Yeah, ideally the solution
3 matches
Mail list logo