RussK wrote: > Thanks for your responses. Before I posted this question, I looked at > awesome_nested_set. But I have two problems with it: (1) my entire > application is largely a tree, but the nodes are of different classes > at different levels, and the nested sets need all nodes to be of the > same or a derived type,
That's easily worked around. Don't discount nested sets on that basis. > (2) the tree here is almost always flat, Um, how can a tree be flat? > making the nested set solution way overkill. It's not overkill. It's the fist structure you should think of when you have anything treelike. You're trying to reinvent the square wheel with your approach, I think. That said, I'll try to answer your question in more detail when I have time. 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 -~----------~----~----~----~------~----~------~--~---
