Rob I don't believe YAGNI applies here but "favour composition over inheritance" sure does. It's just up to you how you treat your models, as simple extension of the data, or an entity that can be persistent in a database (or somewhere else). So I totally agree with Bill that this is a bad idea. And it really doesn't cost much to avoid it.
Regards Karol Rob Allen-3 wrote: > > Karol Grecki wrote: >> Hi Rob, >> >> Applications tend to evolve, often beyond what you expected. > > Of course. > >> 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 >> > > Strikes me as a case of YAGNI. If at some point in the future you need > your press-releases model to start supporting SOAP, then that's the time > to refactor. > > I was mainly commenting on the blanket comment by Bill that using Active > Record (i.e. Zend_Db_Table / Zend_Db_Table_Row with business logic in > it) is a bad idea. > > Regards, > > Rob... > > -- View this message in context: http://www.nabble.com/Data-models-tf4116540s16154.html#a11731670 Sent from the Zend Framework mailing list archive at Nabble.com.
