Yeah, if you have associated models, particularly when they are functionally reliant (as yours are), I think it is perfectly acceptable for them to reference each other. Of course, they should each contain their own unique functionality, but supply an interface for other models.
On Sep 12, 12:01 am, MikeK <[EMAIL PROTECTED]> wrote: > Thanks Grant -- I wasn't sure about that but it worked well. Since the > User (or Angler in my case) is associated with Scores and Catches, all > I needed to do was have my afterSave routine in the Catch model pass > the $this->data['Catch'] to the routine in the Angler model. The > routine in the Angler model read the Angler (using the id in the Catch > record) and this caused all the associated Catch and Score records to > load, at which point I could do my thing then update the Score. > > What confused me was the ability to update another model (Scores) from > within Angler, but I guess it's copacetic because they are associated? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
