A model is usually the layer in the application which holds the data in the application. For instance in your example of a login, a view would have a form, a controller would generate the form & listen to the submission of the form, but the controller would query against the model to see if the user credentials are correct. A very nutshell version.
http://framework.zend.com/manual/en/zend.db.table.html is a good place to start,
I actually just wrote up a peice but it covers normalized tables on top of zend_db_table_abstract:
http://joshteam.wordpress.com/2008/05/13/zend_db_table-with-normalized-tables/Hope this helps!
On Tue, May 13, 2008 at 10:41 AM, Rishi Daryanani <
rishijd@...> wrote:
Hi,
I'm a total newbie, but I am reading up on the Zend
framework and trying out some tutorials, very useful..
However everything I've read/tried involves the
"application/views" and "application/controllers"
directories to create views and controllers. I have
not yet come across any mention of the "models"
subdirectory.
Where can I learn more about this and what it's used
for?
Am I right in assuming that I can build my own
functionality (e.g. user login form, CMS) entirely
with the concept of a controller and view? (but not a
model)
Many thanks
