Frederick Cheung wrote in post #962721: > On Nov 19, 12:23pm, Marnen Laibow-Koser <[email protected]> wrote: > >> used it, but has probably been fixed by now. awesome_nested_set lives >> up to its name. >> > > Although nested sets make inserts very expensive.
So use nested intervals instead. They fix that problem completely. > Like most data > modelling questions, the sort of access patterns that will be used - > while acts as tree makes getting a whole subtree expensive, if you > never need to do that in your app, who cares? If you never need a whole subtree, you probably don't need a tree structure in the first place (though there are exceptions). > > Fred Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] Sent from my iPhone -- 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.
