On Sun, Jul 13, 2008 at 10:27 AM, the_woodsman <[EMAIL PROTECTED]> wrote: > > I can think of a few reasons- perhaps to abstract a complex database > relationship into a single entity in most of the codebase? > > A model can use its related tables, i.e if Post hasMany Comments, in > the Post model you can use $this->Comment. > > You can also load arbitrary models on the fly using App::import. > > And of course you can do this abstraction at the DB level using a > MySQL view to join tables. > > If Dardo has any other tricks for this, I'd be interested too! >
I was thinking in set $this->useTable and overriding the Model::schema() to do a caching in a table basis (or force reloading). > > > On Jul 12, 3:27 pm, "Dardo Sordi Bogado" <[EMAIL PROTECTED]> wrote: >> > it's possible to use one model with more than one different tables? >> >> Technically yes, but doesn't make any sense. Can you explain why? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
