I dont know if its even possible but id really like to see some general abstraction for ORM integration that these would be based on... Just to make it easier to integrate Propel for instance.
Granted this would have to be pretty abstract given vendor differences - or even differences in major versions of the same software. Im just thinking that if i want to integrate ORM XYZ, i should general interfaces/abstractions for Model Builders, Form Builders, Loggers and what not to program to make the process just a little less daunting. Sorry to see Zend_Entity go, but I readily welcome Doctrine :-) weierophinney wrote: > > -- Antonio José García Lagar <a...@garcialagar.es> wrote > (on Thursday, 29 October 2009, 07:24 PM +0100): >> I'm so sorry for this decision but otherwise I know this was a hard work >> that >> you have done mostly alone. >> >> Although the project is not finished, I congratulate you: your work has >> been >> excellent. >> >> Do you plan to integrate Doctrine 1.x with ZF? I think that I'm not the >> only >> one tied to PHP 5.2. I hope to help with this. > > 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.). > > -- > Matthew Weier O'Phinney > Project Lead | matt...@zend.com > Zend Framework | http://framework.zend.com/ > > -- View this message in context: http://www.nabble.com/Discontinuing-Zend-Entity-in-favour-of-Doctrine-integration-tp26117819p26118942.html Sent from the Zend Framework mailing list archive at Nabble.com.
