Hi Tristan, I think (4) doesn't work properly because of (3). Unfortunately,
I don't have Lime or any other unit testing framework set up right now.
However, the error would usually occur when I did the following:
1)make new root (no problem)
2)add children to root (no problem)
3)add grandchildren to one of the children (using InsertAsLastChildOf() or
InsertAsFirstChildOf()). At some point after adding a grandchild, the parent
or one of its siblings got its tree_right values incremented to a value
greater than the tree_right value of the root. When this would happen was
not always predictable though. Sometimes I could add quite a few
grandchildren before I got problems.

I am sorry I can't be more specific than that. Maybe it is just a problem
specific to my own test data. It doesn't sound like anyone else has had this
problem.

In the meanwhile though I in the process of setting up and testing
edge-adjacency as an alternate hierarchical model for my application.
http://www.artfulsoftware.com/mysqlbook/sampler/mysqled1ch20.html#adjacency_
list_model 

The reason for this is not your plugin but instead I expect there to be a
lot of updates and revisions to my trees and branches, possibly by multiple
authors who are working on the same tree at the same time, ouch! NestedTree
appears to be better suited to hierarchical trees that are are seldom
updated or revised. Edge-Adjancency appears to get around the multiple query
issue of standard adjacency models by storing the relationships in a
seperate table which you can query once to get the whole tree just like the
NestedSet model. Anyway, my head hurts just thinking about it. Wish me
luck...

--peterVG


 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" 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/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to