Bill Karwin wrote: > Right; I don't believe it's appropriate to assume that a "model" can > simply extend a table or row object. It's better to write your own > model class, extending nothing, that may use a table or row object, and > may also use other sources of data, such as a SOAP service. >
I would disagree with this. There is a large set of applications where extending Zend_Db_Table and Zend_Db_Table_Row will provide an excellent model. Writing another class that is essentially a proxy to the database class would not be worth the effort. Obviously, there is another set of applications where a completely independent model is the right way to go, but I don't think that it's the case where every model requires it. Regards, Rob...
