We're stuck in a loop :) Let me recap the use case:
1. Developer A creates a new data model [with autogeneration in place during development]. 2. Developer A finalizes their code and tests, commits their model. 3. A hook generates the proxies in the model. 4. Developer B pulls the model as a dependency in their app, when the proxies are requested, they're already there. In my use case, Developer B *can't* modify the model code, so it would be pointless to worry about caching those proxies, the cache would *never* change, so why generate them on the application level, what is the benefit. Sorry this took so long :) Thanks On Monday, April 13, 2015 at 12:30:01 PM UTC+3, Marco Pivetta wrote: > > On 13 April 2015 at 10:24, Badr Ghatasheh <[email protected] > <javascript:>> wrote: > >> What caching? >> > > Proxies *are* cached generated code > > 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.
