If the model you need can be found as the child of another model, use that one.
Its the same as creating a new object of the same name. But using the previous method stops you from instantiating duplicate objects. On Feb 12, 1:07 pm, Dave <[email protected]> wrote: > Just wondering if there is a performace loss when "chaining" models > together such as $this->User->Player->Team->Division > > as oppsed to > Controller::loadModel('Division'); > $this->Division->function($foo, $bar); > > Is it better to flow thru the relations or just grab the data directly > rather than going thru the relationships if you need data from the end > Model? Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. 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
