From: JT S. <jt...@pl...> - 2004-07-03 15:53:28
|
>>> Is there a reason to keep the the "forrest" model if we are going for >>> the Nested Set model? >> >> The way pages work in WebGUI force you to use a forrest model. Every >> page-root is actually a seperate tree. Those are bound together with a >> (non-exeistent) node with pageId=0. If you want to drop the forrest >> model, you'll end up having one (existent) 'master' page (ie. only one >> page root) under which alle the other pages are hung. > >Yes, but same result could be achieved with one root. It will also make things easier >when moving nodes. From a performance view, the forrest model is better as it will >lower the number of affected rows when updating. If it helps anything, there's no reason we couldn't put a master root page in the database with an ID of 0 and a parent ID of -1. JT ~ Plain Black Create like a god, command like a king, work like a slave. |