Re: Storing dynamic attribute data in a db

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



At 1/18/2007 02:56 PM, Chris W. Parker wrote:
I'm currently working on trying to find a solution that is both simple
and flexible for storing the data of a complicated set of dynamic
options for some of our products. My current thinking is that I will use
Modified Preorder Tree Traversal to organize the data.


Are you considering keeping all the levels of your data tree in a single table because you can't predict how many levels there will be? If you CAN predict its depth, wouldn't it be simpler and easier to conceive, code, and debug with N tables chained in parent-child relationships?

I'm not asking rhetorically but seriously, for discussion. How are you weighing the pros & cons of using MPTT?

Regards,
Paul
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux