On 13 April 2015 at 08:08, Badr Ghatasheh <[email protected]> wrote:
> Thanks Marco, > > I'm failing to see the difference here, I want them created post-pushing > new models, you're saying they should be prepared pre-deployment, there are > no steps in between, the code is still generated and *not* modified, and > the only variable in the equation that forces you to regenerate them is a > modification to the entity itself, which will *never* be modified in > application. > > The applications I'm working on have very high concurrent users, using > AUTOGENERATE_EVAL is not a valid solution, in fact, using any type of > autogeneration is not an option. > > Whenever you turn off autogeneration, proxy files stops being a cache and > they become a dependency, which gets me back to square one. > > Let me put it that way, why use a high maintenance solution when you can > do a transparent one at the same cost? > > Badr > Because caching is hard, and when you have a stale cache, you have a problem. Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
