-- Jon Lebensold <j...@lebensold.ca> wrote
(on Thursday, 03 December 2009, 04:39 PM -0500):
> I think that in the architecture you're suggesting, it makes a lot of sense,
> however I wonder how many apps need per-module models since you're essentially
> creating two resource layers: one "system-wide" one and one for that
> particular
> portion of the application. If you're manipulation of a subset of data (in
> your
> case, scrum logs) with module-specific business rules, then its a no-brainer.
>
> When I did the zendcast, I was heavily inspired by your blog post about zend /
> doctrine model autoloading, however I didn't find a working example with
> models
> being generated on a per module basis using the CLI.
I actually don't generate my models -- I define the entities explicitly,
and go the other route: generating my DB schema from the models. I've
done that from the CLI, but I think I can find better ways to do it.
> On Thu, Dec 3, 2009 at 4:02 PM, Matthew Weier O'Phinney <matt...@zend.com>
> wrote:
>
> -- Jon Lebensold <j...@lebensold.ca> 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 <admi...@gmail.com> 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 | matt...@zend.com
> Zend Framework | http://framework.zend.com/
>
>
--
Matthew Weier O'Phinney
Project Lead | matt...@zend.com
Zend Framework | http://framework.zend.com/
