Hi Rob, Applications tend to evolve, often beyond what you expected. Creating a proper model that is decoupled from a database is not that much effort. And it may benefit you greatly if you're building non trivial application
Regards Karol Rob Allen-3 wrote: > > 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... > > -- View this message in context: http://www.nabble.com/Data-models-tf4116540s16154.html#a11729637 Sent from the Zend Framework mailing list archive at Nabble.com.
