On Feb 22, 2008, at 6:59 PM, jim starboard wrote:
> > "As far as I know, there's no need for multiple-table models " > > Why? that seems overly simplistic. It is. :) > ORM should allow a data > representation where setting a single property might update several > tables. It does. Check into model callbacks in the manual. > Why should my controller need to access multiple models when I > should be able to access a single model that in turn references > several tables (or child models). It may, but you can set it up how you'd like. I can't recommend touching too many tables with a single operation - if your domain logic for a given set of data is strewn and shared between classes, it's harder to place things and fix problems. -- John --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
