Sigh.........

Just when I thought I had the MVC thing done and dusted.
I'm fairly sure there was another thread where the general thought was that anything related to data should be done in the Model and the controller should be used as the "glue" between the model and the view. I've just delayed a project in order to port all or my controller data manipulation into the model and am disheartened to hear this could be the wrong thing to do :-(
Someone please tell me they are doing the same as I am!

Sigh again.......

A positive thing I've found about moving this kind of logic into the Model is that it makes it possible to write unit tests for these functions using the existing test suite. Testing controllers with the current setup is bordering on impossible.

Cheers,

Sonic.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cake-php
-~----------~----~----~----~------~----~------~--~---

Reply via email to