In a bigger application, there can be many tables with many associations. In this example, there are Forums with Posts. Some of the database associations might not be used; for example, a User hasMany Posts, but I will rarely need or want the Posts to be fetched when I just have a User. That incurs a lot of overhead, especially in the case of Posts.
I realize $recursive is there, and that there are ways to "unbind" associations on-the-fly (I think cakebaker pointed that out in a post). But it seems that there are way too many associations that I'll only need rarely in a particular model. Maybe my thinking goes against the nature of MVC. My main concern is optimization. It would seem easier to only enable certain associations during queries...but perhaps my thinking is off-base. How can this be optimized so that the application can scale well? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
