Question about efficiency about baum HOT 3 CLOSED

Nested Sets are generally for hierarchical data like categories. If you don't need your tags to be hierarchical, then Nested Sets are probably over kill.

If you do need to get the data in it's hierarchical fashion (as a tree for categories for example) then nested sets (in my opinion) are the best way to go. Especially if the hard work is done as it is with this project.

There are easier ways to manage tags owned by different organisations as long as you don't need them to have parents or children. Look up Many to Many relationships (http://laravel.com/docs/eloquent#many-to-many) using a pivot table.

from baum.

@SiCoUK answered your question pretty well here.

A nested set implementation is usually pretty fast when querying hierarchy chains (ascendants, descendants), and slow when performing inserts/updates because of the index bounds re-computation. So, NestedSet structures are good when your use-case requires hierarchical structures which are queried far more often than modified (inserted/updated).

Also as @SiCoUK said, if your tag data implementation does not need to be hierarchical there's no need to use a nested set structure for that.

from baum.

I think your question has been answered so I'm closing this issue for now. Please, feel free to reopen or open a new issue if you've got more questions.

from baum.