Obie Fernandez wrote:
> I was looking into using acts_as_nested_set last week and decided
> against it (for now) because my application is very insert-heavy. The
> way that acts_as_nested_set is currently implemented will cause a lot
> of db thrashing unless your tree structure is relatively stable.
>
> For more info, read the second half of this page:
> http://searchoracle.techtarget.com/tip/1,289483,sid13_gci537290,00.html
One thing I am wondering about:
If your tree structure is very stable you will likely be able to cache
it anyway, won''t you?
So I am wondering if doing the switch really changes performance much in
real world scenarios...
Thanks for the link, it contains some valuable information and I think
that the conversion query will help me when I finally decide to do the
switch to nested sets.