[fw-general] Zend_Db_Mapper Proposal - Ready for Review
Hello everyone, I finished up a new proposal that would greatly enhance domain driven development with the ZF: A generic data mapper component. http://framework.zend.com/wiki/display/ZFPROP/Zend_Db_Mapper+-+Benjamin+Eberlei Its a contrasting proposal to Zend_Db_Table, for handling the underlying persistence of your application layer. Its aiming at enterprise developers that need to do more than the usually siple BlogPosts <-> Comments <-> Tags examples. The core concept is the Record (Entity Pattern) centric datastrcuture, rather than the SQL datastructure. You build your applications domain logic of record objects that communicate to each other and then persist them into the database at the end of your session with following a defined mapping scheme. This component therefore tries to achieve the separation of Business logic from the underlying persistence. comments are greatly appreciated, Benjamin -- Benjamin Eberlei http://www.beberlei.de
Re: [fw-general] Zend_Db_Mapper Proposal - Ready for Review
Do you have any source code laying around anywhere for us to look at? I had some aspirations to write an ActiveRecord component, but my recent experience with models (well, and PHP's lack of late static binding support) has led me searching for other model components. I would love to replace Zend_Db_Table with yours in my applications! beberlei wrote: > > Hello everyone, > > I finished up a new proposal that would greatly enhance domain driven > development with the ZF: A generic data mapper component. > > http://framework.zend.com/wiki/display/ZFPROP/Zend_Db_Mapper+-+Benjamin+Eberlei > > Its a contrasting proposal to Zend_Db_Table, for handling the underlying > persistence of your application layer. Its aiming at enterprise developers > that need to do more than the usually siple BlogPosts <-> Comments <-> > Tags > examples. > > The core concept is the Record (Entity Pattern) centric datastrcuture, > rather > than the SQL datastructure. You build your applications domain logic of > record > objects that communicate to each other and then persist them into the > database > at the end of your session with following a defined mapping scheme. > > This component therefore tries to achieve the separation of Business logic > from the underlying persistence. > > comments are greatly appreciated, > Benjamin > > -- > Benjamin Eberlei > http://www.beberlei.de > > -- View this message in context: http://www.nabble.com/Zend_Db_Mapper-Proposal---Ready-for-Review-tp21652525p21700669.html Sent from the Zend Framework mailing list archive at Nabble.com.
Re: [fw-general] Zend_Db_Mapper Proposal - Ready for Review
Hello, i don't have any source code to look at currently. Since this is still a proposal and final features can have a huge impact on how the query select and persist engine will look like. I am trying to get a prototype and an example running for this proposal though to add some more advanced Use-Case snippets for public review. greetings, Benjamin On Wednesday 28 January 2009 07:34:22 Ken Chau wrote: > Do you have any source code laying around anywhere for us to look at? I had > some aspirations to write an ActiveRecord component, but my recent > experience with models (well, and PHP's lack of late static binding > support) has led me searching for other model components. I would love to > replace Zend_Db_Table with yours in my applications! > > beberlei wrote: > > Hello everyone, > > > > I finished up a new proposal that would greatly enhance domain driven > > development with the ZF: A generic data mapper component. > > > > http://framework.zend.com/wiki/display/ZFPROP/Zend_Db_Mapper+-+Benjamin+E > >berlei > > > > Its a contrasting proposal to Zend_Db_Table, for handling the underlying > > persistence of your application layer. Its aiming at enterprise > > developers that need to do more than the usually siple BlogPosts <-> > > Comments <-> Tags > > examples. > > > > The core concept is the Record (Entity Pattern) centric datastrcuture, > > rather > > than the SQL datastructure. You build your applications domain logic of > > record > > objects that communicate to each other and then persist them into the > > database > > at the end of your session with following a defined mapping scheme. > > > > This component therefore tries to achieve the separation of Business > > logic from the underlying persistence. > > > > comments are greatly appreciated, > > Benjamin > > > > -- > > Benjamin Eberlei > > http://www.beberlei.de -- Benjamin Eberlei http://www.beberlei.de
