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 On Monday, April 13, 2015 at 2:40:50 AM UTC+3, Marco Pivetta wrote: > > On 12 April 2015 at 17:28, Badr Ghatasheh <[email protected] > <javascript:>> wrote: > >> The problem is: users of the model shouldn't worry about maintaining the >> proxies, they should not know about them or worry about how they work. >> > > I think you misunderstood the problem: proxies are *not* a dependency of > your code - they are a cache. > > You don't commit caches to the SCM: you warm them up pre-deployment > instead, and they are built specifically for the deployment environment. > > If you don't want the user to know anything about the proxies at all, then > use AUTOGENERATE_EVAL, and you'll never hear about them again (except from > performance reports, since you just killed the cache). > > Treat proxies like a cache, that's all what they are. > > 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.
