You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't understand, why there cannot be a proxy. But ok, let's say that for some internal implementation reason there canno be a proxy yet. That means there should be at least an exception raised, when validating schema, telling me this crucial information.
Doing a select over 500 entities would result in 501 queries just because I didn't know about this.
If the validator would tell me, I'd join the entity and had 1 query executed.
Resoltion: you shouldn't allow me to define the association as lazy, or use proxies.
Thank you.
The text was updated successfully, but these errors were encountered:
Jira issue originally created by user hosiplan:
Here is a note that "Inverse side of x-to-one can never be lazy"
https://github.com/doctrine/doctrine2/blob/29d6da0fa063d55d06117045f3446b2716202d2b/lib/Doctrine/ORM/UnitOfWork.php#L2587-L2588
I don't understand, why there cannot be a proxy. But ok, let's say that for some internal implementation reason there canno be a proxy yet. That means there should be at least an exception raised, when validating schema, telling me this crucial information.
Doing a select over 500 entities would result in 501 queries just because I didn't know about this.
If the validator would tell me, I'd join the entity and had 1 query executed.
Resoltion: you shouldn't allow me to define the association as lazy, or use proxies.
Thank you.
The text was updated successfully, but these errors were encountered: