On Tue, 8 Jul 2008, Piotrek Karas wrote: > Derick Rethans wrote: > > On Tue, 8 Jul 2008, Piotrek Karas wrote: > > > >> Would it be possible to use Tree component to store and manage in one db > >> table multiple trees (multiple root nodes)? For example, by adding a > >> special key that would identify records that belong to one tree, or > >> another, for example: > > > > It would be very hard to change to this - why can't you just use > > multiple tables for multiple trees? > > I'm planning a datatype for eZ Publish that for each > contentobject_id/classattribute_id combination (or simply for each > content object attribute) will have a separate tree. Now, if that > datatype becomes popular in terms of objects (I expect more than 10k), > this would mean as many trees... > > I just thought it would be great to solve this problem with the > component, but on the other hand, I don't expect single trees to be very > complex. Also, the management model will not have to be advanced, so > after all I may go back to writing my own code for that.
So why don't just just make one tree where the roots of your trees are basically the first sublevel? regards, Derick -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
