Hi Darby, Thanks, this was the closest response to what I was looking to achieve. Although the other posts have prompted me to redesign my models because of the problems/improvements suggested.
I think that the Data Mapper is what I'm looking for... but now I know the pattern to look at, there is still little information out there about an actual implementation and some concrete examples. The patterns always look so elegant on paper but I end up battling them out with my code and when I'm finished I still don't know how closely I have followed the pattern. My research has pointed me towards this article from the Prado site http://www.pradosoft.com/demos/quickstart/?page=Database.SqlMap This looks like a really neat way to organize an ever complex system of objects. I will study the implementation further. Has anyone involved with the Zend Framework ever considered proposing a Zend_Data_Mapper? Cheers, Sam Darby Felton wrote: > > Depending on your needs and the complexities of your applications, it > may be worth investigating the Domain Model pattern [1]. Simple Domain > Models may use Active Record [2] (Table Data Gateway [3] + Domain > Logic), whereas more complex Domain Models need Data Mapper [4] and/or > Service Layer [5]. > -- View this message in context: http://www.nabble.com/Models%2C-Objects-and-RDBMS---Best-Practise-tf4052812s16154.html#a11529924 Sent from the Zend Framework mailing list archive at Nabble.com.
