Yes, that does make sense. I ended up just putting a *switch
(getEnvironment()) { ... }* statement atop my Application.cfc. This *seems* to
achieve what I want and allow reloading the framework per request in
development.
Thank You,
Matt
On Thursday, November 15, 2012 1:11:18 PM UTC-7, Sean Corfield wrote:
> Use an application variable to figure out whether you've run your "one
> off" stuff - and reset it in setupApplication() so when you reload the
> framework, it will re-run it on the next request.
> Make sense?
> Sean
> On Thu, Nov 15, 2012 at 1:00 PM, fingerskier <finge...@gmail.com<javascript:>>
> wrote:
> > Hello,
> > First of all, I'm really glad to see this feature.
> > I would like to automatically handle ORM settings based on
> environment.
> > However, according to the docs setupEnvironment() is "executed on every
> > request". So, I have to run ORMreload() to make the changes stick but
> a
> > setting like dbcreate="dropcreate/update" on my dev-server makes that
> > untenable. Am I stuck hard-coding these settings? or, is there another
> way
> > [within the framework]?