I think you'd be interested in the Tree Behavior:
http://api.cakephp.org/class_tree_behavior.html
This particular behavior implements arbitrarily deep tree structures
stored in a database using a modified pre-order tree traversal graph
algorithm, which essentially reduces the number of queries to get your
tree (or a subset thereof) to one.  The trade-off is that there is a
slight performance cost to node insertions and deletions.

hth.
-Joel.

On Aug 21, 4:38 pm, LarryTX <[EMAIL PROTECTED]> wrote:
> I've been using Ruby on Rails for quire a while, having been forced
> into it primarily because of its excellent support for nested sets.
> However, I'm increasingly disenchanted with it because it seems to
> break everything every time a mine release occurs -- a sign of a
> product that is far from mature. In addition, its hosting requirements
> are excessive. I'm looking at going back to PHP as my primary server-
> side language and the possibility of CakePHP as my framework.
>
> Before I can do that, I need to know, what kind of support is there
> for nested sets? I'm using nested sets for hierarchical categories of
> n-depth, so I'm not very interested in the ability to produce nicely
> indented HTML listings or breadcrumb menus. I need easy maintenance of
> the categories table with the selection of arbitrary parents and easy
> assignment of categories with a display constructed of the category
> plus its ancestry, such as "Computera > Programming Languages > PHP >
> Forms"
>
> Hope all that makes sense. This information as well as any other
> impressions you might have about migrating from RoR to Cake would be
> most appreciated.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CakePHP" 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/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to