-- Jon Lebensold <[email protected]> wrote (on Thursday, 03 December 2009, 03:34 PM -0500): > not true... I put the Doctrine CLI script in a /scripts folder. All the other > folders (migrations / sql / yaml / data) I believe belong in configs/ since > they are part of setting up an app or migrating releases. > > the models belong in /model > > I haven't found a good solution to autoloading /modules/{modname}/models yet
I've found that having ZF do the autoloading for your models works flawlessly, and can thus simply use the autoloading rules defined in Zend_Application_Module_Autoloader (which module bootstraps instantiate and configure by default). > Also, I wonder how many module-specific models most app's have (and > I'm eager to see how D2 / ZF2 integration will standardize these > things). In the scrum app I've been working on, I had an "application" module (the default module, basically) that had models related to users and teams; these were considered "system-wide" models. I then had models specific to the "scrum" module (which has functionality for manipulating backlogs, sprints, and scrum logs). I'm also planning a pastebin and wiki module for this application -- and each module thus has its own models. > On Thu, Dec 3, 2009 at 2:57 PM, takeshin <[email protected]> wrote: > > > Where do you store models, migrations, sql, yaml, > cli scripts etc. when using Doctrine (1.2) with ZF. > > I noticed on zendcasts.com, > that Jon puts a lot to /application/configs/ > > It makes me wonder > > -- > regards > takeshin > -- > View this message in context: http://n4.nabble.com/ > Doctrine-default-directory-structure-tp947943p947943.html > Sent from the Zend Framework mailing list archive at Nabble.com. > > -- Matthew Weier O'Phinney Project Lead | [email protected] Zend Framework | http://framework.zend.com/
