Hi, Also, this is my resource which i use: http://pastebin.com/d207ac465
Just add to config: resources.database.connection_string = "mysql://user:p...@localhost/db" resources.database.compiled = false; use compiled version of Doctrine It enables autoloading for models and tables, utf-8 for connection, validation on save and dql callbacks. P.S. It expects Doctrine to be in library/Doctrine/Doctrine.php. It is like that because i use svn:externals to update doctrine and don't want to have it straight in my library folder -- Juozas Kaziukėnas ([email protected]) Aš internete - JuoKaz (http://www.juokaz.com) On Fri, Oct 30, 2009 at 7:30 PM, A.J. Brown <[email protected]> wrote: > For those that are interested in my resource class: > > http://gist.github.com/222645 > > I'm also working on making a resource for the CLI components, so that > you can do deployments from within your Zend Framework application. > For example, if the environment is a testing server, the application > will automatically do a build-all-reload. Or perhaps the application > will automatically run migrations when new ones are detected. > > This is just a starting point. > > On Fri, Oct 30, 2009 at 1:23 PM, Matthew Weier O'Phinney > <[email protected]> wrote: > > -- keith Pope <[email protected]> wrote > > (on Friday, 30 October 2009, 04:43 PM +0000): > >> 2009/10/30 Matthew Weier O'Phinney <[email protected]>: > >> > -- keith Pope <[email protected]> wrote > >> > (on Friday, 30 October 2009, 04:02 PM +0000): > >> > > 2009/10/30 Ralph Schindler <[email protected]> : > >> > > Also will we be deprecating Zend_Db as if we have tight Doctrine > >> > > integration is there any reason to keep Zend_Db? > >> > > >> > There are plenty of reasons to keep Zend_Db. Not everyone will be > using > >> > Doctrine, and for many one-off types of applications (single tables, > or > >> > multiple tables with no relations, etc.), having Zend_Db around will > >> > continue to be essential. Additionally, one aspect I'd like to explore > >> > with the Doctrine folks is potentially allowing Zend_Db adapters as > >> > Doctrine RDBMS adapters; this would provide some very interesting > >> > integration points. > >> > >> Sounds interesting I look forward to seeing this initiative develop > >> further, I would be happy to help in any way I can :) > >> > >> Once we have the integration especially with doctrine 2 would there be > >> any further plans to look at things like dependency injection, > >> criteria objects and repositories or any other DDD tools? To me having > >> a full suite of tools like this would be a great long term goal? > > > > DI is something we're already planning for -- you'll note the "unified > > constructor" pattern in all new components. Whether or not we'll have a > > DI _container_ is another question; I'm not entirely convinced DI > > containers have a good place in stateless applications, but I'll let > > Ralph talk more to that point. :) > > > > As for criteria objects, we've just approved another of Ben's > > components, some extensions to Zend_Db_Expr. One aspect I particularly > > like with it is that, combined with Zend_Db_Select, we are getting to a > > point where we have an almost complete criteria object for select > > operations. This could certainly be adapted for use with DDD fairly > > easily. Regarding repositories, Zend_Application_Bootstrap actually > > already acts as one in many ways -- though we may do more with this > > and/or service locators for 2.0. > > > > -- > > Matthew Weier O'Phinney > > Project Lead | [email protected] > > Zend Framework | http://framework.zend.com/ > > > > > > -- > A.J. Brown > web | http://ajbrown.org > phone | (937) 660-3969 >
