Nope, what you're doing makes complete sense. The purpose of the
controller is to act as the "glue" between the model and the view. The
controller can also aggregate and operate on other types of data as
well, and for some of the logic, you need data outside the model, i.e.
session data, so it m
EDIT:
Then my controller would be mostly lines like:
$this->set('widgets', $this->Widget->getAllWidgets());
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake
I'm fairly new to OO development, and I'm probably overthinking this,
but ...
The manual explains [find($x), findAll($x), findAllBy($x)] as model
functions which leads me to want to put all of my dbaccess logic there,
within functions like getAllWidgets, getSubWidgets, etc.
Then my controller wo
