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
All DirectWrite[xx]Store have an implementation of eObject(Id) that looks in the cache if the object has been loaded to avoid database calls. However, the cache lookup is initialized with new PersistentEObjectCacheLoader(eClass), that is called if the cache does not contain the requested element.
The eClass parameter of the loader forces the framework to find the EClass of the object in the backend before the cache lookup. This is not useful if the object is in the cache.
A more efficient implementation would be to initialize the PersistentEObjectCacheLoader with the id, and compute the corresponding EClass only if we need to load the object from the database (in the apply method).
The text was updated successfully, but these errors were encountered:
All DirectWrite[xx]Store have an implementation of
eObject(Id)
that looks in the cache if the object has been loaded to avoid database calls. However, the cache lookup is initialized withnew PersistentEObjectCacheLoader(eClass)
, that is called if the cache does not contain the requested element.The
eClass
parameter of the loader forces the framework to find theEClass
of the object in the backend before the cache lookup. This is not useful if the object is in the cache.A more efficient implementation would be to initialize the
PersistentEObjectCacheLoader
with theid
, and compute the correspondingEClass
only if we need to load the object from the database (in theapply
method).The text was updated successfully, but these errors were encountered: