I asked nearly the same question today, although mine was geard more towards setting up a single CLI entry point for building without having to create a Zend_Tool_Provider and all that mess... Heres the thread from the Doctrine user list:
http://groups.google.com/group/doctrine-user/browse_frm/thread/731db48058b88821 I havent had a chance to try all this yet as ive been focused on getting the builders hooked up properly since thats sort of essential for my particular project going forward. Id be interested if all the other details he provided end up working out for you as ill be wrangling with those later this week. Jurian Sluiman-2 wrote: > > Hi guys, > I'd like to implement Doctrine with my ZF app. Integration with an > application > resource isn't that hard. The difficulties are with the modular ZF > structure > and > the non-modular Doctrine model folder. > > Since 1.2 Doctrine is capable of PEAR style loading of models and > generation. > But the naming convention is e.g. Blog_Model_Article and the path is > blog/models/Article.php. Hence the difference between blog <> Blog and > models > <> Model. > > Doctrine likes to keep all schemas, sql and fixtures inside one folder. > I'd > like to keep my application modular, so having separate schemas, fixtures > and > sql scripts inside each module. Even migrations on a module base seems > quite > useful to me. > > Is there any experience in having Doctrine tightly integrated into a ZF > application, with a complete separation of module based models? Many blog > posts are explaining the very basics, but that isn't the hardest part at > all. > > Regards, Jurian > > -- View this message in context: http://n4.nabble.com/Experience-with-modular-Doctrine-structure-tp955923p956433.html Sent from the Zend Framework mailing list archive at Nabble.com.
