Doctrine 2 - ORM

Result cache should cache the SQL result and not the final objects

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.0-ALPHA3
  • Fix Version/s: 2.2
  • Component/s: ORM
  • Security Level: All
  • Labels:
    None

Description

When fetching objects and using a result cache, it would probably be better to cache the SQL result array instead of the hydrated objects. That way, when grabbing from the cache managed entities can be returned. Also, caching is more efficient since an SQL result array does not need to be serialized/unserialized when storing in apc or memcached.

Issue Links

is duplicated by

Improvement - An improvement or enhancement to an existing feature or task. DDC-1279 Shouldn't Cached Results Trigger LifeCycleEvents?

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
is referenced by

Improvement - An improvement or enhancement to an existing feature or task. DDC-446 Cached resultset do not add Entities in UnitOfWork

  • Major - Major loss of function.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

People

  • Assignee:
    Benjamin Eberlei
    Reporter:
    Roman S. Borschel
Vote (5)
Watch (6)

Dates

  • Created:
    Updated:
    Resolved: