-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DDC-3407: add possibility to prevent some entitiy methods from being proxied #4211
Comments
Comment created by @Ocramius: I wouldn't implement it that way. I'm actually building something (non-trivial) at Ocramius/ProxyManager#192 and Ocramius/ProxyManager#159, but it will take some time to get there, and also to get doctrine to use that component to generate proxy classes. |
@Ocramius Is their any update on this? From what i have seen the ProxyManager implemented the needed groundwork quite a while ago, are their any plans to make them available in the orm? |
Hmm, is it better to do a broad/generic "non-initializing methods" feature, or would it be better to have a narrower way to specify "this method is a primary-key getter"? |
well if you use the proxymanager of ocramius the lazy loading is done on accessing props not methods |
#1241 is attempting to solve this issue as well |
Solved in #6719 |
Jira issue originally created by user backbone:
This is for optimization of lazy loading, when using entity methods that operate only on identifier values.
This issue is partially addressed via:
ba38f3e
But it makes assumptions about a certain code style, that is for an "id" identifier property the getter is named "getId". but some code styles prefer "getID".
It would be nice to have an annotation like @Orm\SkipProxy (or equivalents for xml/yaml) to mark a method that should not be proxied.
The text was updated successfully, but these errors were encountered: