RE: [PEAR-DEV] DB_NestedSet - What is the rodmap ?

Hello Arnaud, > What is the plan for 2.0 of DB_NestedSet ? (i mean, features, BC breaks or > not, dates and stuff ;) Plans: - Remove the event handlers as they don't seem to make much sense. Me only uses them for onNodeLoad to get additional Data for the node from other Databases. This can now be done with the $addSQL param. All other event catching things could be done on the application side. - Switch to another representation of the NestedSet model. ATM the order within a level is stored and if one moves a node inside this level only this order field is changed. This is the reason why the query methods return a for some users confusing representation of the tree. The only thing I have to solve is the ordering of rootnodes as they can't be ordered using LFT/RGT. I thought the current model is a good idea but I very much emails asking why the data is sorted the way it is. This may lead to BC breaks. - Using the array representation of a node internally instead of using objects. - Simplify the method calls as they got pretty overloaded with params as new features where introduced. This may lead to BC breaks - Totally rewrite the database driver API to support MDB which is broken ATM - Clean up the API and get rid of redundant some redundant pickNode() calls. BC: There may be BC breaks but I'll do my best to cut them low. There will be compatibility flags. Date: How do they say? "It's ready when it's ready...." ;) This will be in 1-2 months. greetings Daniel Khan