Doug Jolley wrote: >> I would generally recommend a nested-set model instead; > > Thanks for the suggestion. I see the nested-set model as being an > alternative to acts_as_tree. Unless I am mistaken they are 2 > different ways of doing essentially the same thing.
Yes. Nested sets are unquestionably the superior alternative -- for example, with nested sets, it is possible to retrieve a node and all its descendants from the DB with a *single* query. This is impossible with the simple adjacency list that acts_as_tree provides. > Both could be > helpful in creating a hierarchical view but neither provides a slam- > dunk approach to that end. What do you mean by a slam-dunk appropach? Something that generates the HTML? So far as I know, you'll have to do that yourself. > > I think I see where I stand. And where is that? > Thanks to all who responded. > > ... doug Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
