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
The current approach of ghost objects is to lazy-load the object when the public API of the object is hit.
This involves that a lot of logic is under-optimized and can cause lazy-initialization even when not needed (for example, when accessing API that doesn't fetch internal object state, or that doesn't rely on the object's lazyness).
To mitigate that, public API lazy loading shall be completely removed, replaced by lazy properties only.
This way, compatibilizing ProxyManager with Doctrine 2 ORM will be easy and effortless.
The text was updated successfully, but these errors were encountered:
The current approach of ghost objects is to lazy-load the object when the public API of the object is hit.
This involves that a lot of logic is under-optimized and can cause lazy-initialization even when not needed (for example, when accessing API that doesn't fetch internal object state, or that doesn't rely on the object's lazyness).
To mitigate that, public API lazy loading shall be completely removed, replaced by lazy properties only.
This way, compatibilizing ProxyManager with Doctrine 2 ORM will be easy and effortless.
The text was updated successfully, but these errors were encountered: