that's just as usable.
I usually use the adjacency list model (really simple to build the backend),
and then build a recordset that has the tree in linear form (a la nested
set model), along with some metadata (like node indexes and counts at each
level), and then cache that in memory. Do that and it's even faster than an
nested set model for certain operations, at the expense of having to
regenerate it when you make changes. It's quite nasty to implement on CF4.5
and less, because they lack QofQs, but on CF5 or CFMX, it's really quite
simple.
Cheers,
barneyb
> -----Original Message-----
> From: Dowdell, Jason G [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 22, 2004 10:43 AM
> To: CF-Talk
> Subject: RE: SQL: hierarchical view of parent child categories
>
> Thanks for the feedback. I have read articles by him before
> and his articles
> were what I used to learn exactly how hierarchical data is
> stored in tables.
>
> Thanks again,
> Jason
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
