Hello Keith, you should take a look at Doctrine 2. As Zend Entity it implements the JPA specification and is a true data mapper with models decoupled from Database completly.
greetings, Benjamin On Thursday 29 October 2009 09:19:50 pm keith Pope wrote: > 29 Matthew Weier O'Phinney <matt...@zend.com>: > > -- Antonio José García Lagar <a...@garcialagar.es> wrote > > > > (on Thursday, 29 October 2009, 08:17 PM +0100): > >> 2009/10/29 Matthew Weier O'Phinney <matt...@zend.com> > >> > >> > >> Ideally, we'll have both Doctrine 1.x and 2.x integration, for this > >> very reason - though likely as separate implementations (Zend_Doctrine, > >> Zend_Doctrine2). There are some commonalities between them that we can > >> leverage immediately (application resources, in particular), and others > >> that will require more collaboration between the two projects (e.g., > >> shared cache objects and loggers, etc.). > > I must say its a shame that ZE is going, I thought it was too bigger a > project for one person, not fair asking for that much commitment from > anyone. > > Time to go back to using Doctrine then :( bye bye nice models..... > > Do you think it would be a good idea to update the Quickstart guide > now to not use the Data Mapper pattern and use doctrine instead? > > >> Do you think this will be available for the 1.10 release? > >> > >> You should update the roadmap at > >> http://framework.zend.com/roadmap/1.10.0 > >> > >> I hope to see an early proposal to start to help. > > > > We're in the very early stages of gathering requirements; I honestly > > don't see it being ready for 1.10. > > > > -- > > Matthew Weier O'Phinney > > Project Lead | matt...@zend.com > > Zend Framework | http://framework.zend.com/ -- Benjamin Eberlei http://www.beberlei.de
