Hey, I have posted a couple of times on getting a hierarchal tree 22 levels 
deep programmed for an MLM company.  My original coding was using too much 
memory, as I was more or less creating a FILO type structure with several 
arrays.  I have looked over the various methods for displaying hierarchal data 
with MySql, and there don't really seem to be many elegant solutions-- the best 
method (according to many) seemed to be creating a column for "lft" & "rgt" 
values as a nested tree structure, which is completely impractical in this 
situation because I would have to re-assign those variable every single time 
somebody inserted a record into my database (which should be many times/day).  
The best method I have found (I think...) is to create a temporary FILO stack 
table using a stored procedure.  I found the syntax here: 
http://www.evolt.org/node/4047  however, I know basically nothing about proper 
syntax for stored procedures, and have really not found a lot that has helped.  
Why, oh, why is this syntax giving me errors?  (other than the obvious change 
the variables to match those in my database).  I'm using navicat 8 for mysql 
for my database interactions, dunno if that could be the cause or not...

Equally as important, does this method of creating a temp table seem  like an 
appropriate solution to my problem?  Will this method even work if I have 
several people wanting to access their genealogy at the same time?  Sigh... I 
feel so over my head... thanks for the help, regardless=).

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
ColdFusion is delivering applications solutions at at top companies 
around the world in government.  Find out how and where now
http://www.adobe.com/cfusion/showcase/index.cfm?event=finder&productID=1522&loc=en_us

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:292091
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to