> That's easily worked around. Don't discount nested sets on that basis.
Working around that would be great for my application overall, as I'd like to turn it into one giant tree across multiple, unrelated classes. How might that be done? > > (2) the tree here is almost always flat, > > Um, how can a tree be flat? The tree typically has a height of zero (just a root). > > 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. Your point is well taken. There is another part of my application that has depth and, being ignorant of nested tree, I wrote that functionality and will definitely refactor with an awesome tree. Oddly, that code seems to work while this part does not. But my question is not about trees, it's about why RoR is returning the wrong value for an association. -Russ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
