I wanted the same thing, but I don't think it's possible.
Yeah, it's expensive, but that's what you get if you want to
keep track of what level each post is in a threaded discussion.
I don't know that this could be done in SQL, but maybe some
guru will step forward and illustrate otherwise.
Check out Lee's post from last night - faster for lookups, but
still a big hit when adding levels to the discussion thread.
If you don't care to display what level each post is at, you
can just sort by the time posted or something like that. That'd
speed things up a lot, but you loose some good functionality.
-Erik
-----Original Message-----
From: DRE [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 15, 2001 9:47 AM
To: Fusebox
Subject: RE: Nested trees, what's going on?
Hi Eric, Ive fiddled with this a bit and found that unless the page you're
recursing to - usually a custom tag- is very simple(which it should be in
your case) it tends to hit the server fairly hard and can be a rather
slow. Just to illustrate, if there were 10 threads, each 10 respones deep,
you would have slightly less than a hundred total individual new scopes and
queries created. One for each individual recursive custom tag
call. Assuming you dont make any new queries in each tag.
I've posted a relating question on a couple of discussion groups with few
results. Here it is: Is there a way to make a sql call that recurses
itself? So that I would make one sql call for the page and its children
and its children(based on a parentid) etc of course in the proper order?
Any help would be appreciated. Thanks. DRE
10:14 PM 3/14/2001 -0700, you wrote:
>Recursive calls to a custom tag. That's the way to do it.
>Each time, changing the parent ID.
>
>
>-----Original Message-----
>From: J. Steven Tripp [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, March 14, 2001 10:01 PM
>To: Fusebox
>Subject: Nested trees, what's going on?
>
>
>I have read, re-read and read again the section in the fusebox book on
>Nested trees. I get the database side of things, but the book doesn't
>explain the SQL side of things very well. It shows a one table example for
>the database and then goes on to show a two table example for the SQL.
>
>I am trying to build a threaded discussion. Messages could go quite deep
>in the parent/child relationship and there are some complex joins down the
>road, but bringing it down to it's most basic level, let's say we have a
>table that has only 3 fields:
>
>PostID <--- Primary Key
>ParentID
>MessageText
>
>What would the SQL statement look like. I have tried many variations on
>the book, but nothing.
>
>Suggesstions? Comments? Questions? Jokes?
>
>-Steve
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
