Doctrine 2 - ORM

Shouldn't Cached Results Trigger LifeCycleEvents?

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Duplicate
  • Affects Version/s: 2.1
  • Fix Version/s: None
  • Component/s: ORM
  • Security Level: All
  • Labels:
    None
  • Environment:
    Ubuntu 10.04, PHP5.3

Description

To replace the need for database triggers, we use separate subscribers to, upon @PostLoad, add data that's loaded from other sources.

However, if using result caching, these events are never triggered.

Issue Links

duplicates

Improvement - An improvement or enhancement to an existing feature or task. DDC-217 Result cache should cache the SQL result and not the final objects

  • 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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Eric Clemmons added a comment -

I'd be happy to submit a PR, but I want to be sure that my expectation of @PostLoad being called applies to deserialization as well as hydration...

Show
Eric Clemmons added a comment - I'd be happy to submit a PR, but I want to be sure that my expectation of @PostLoad being called applies to deserialization as well as hydration...
Hide
Permalink
Benjamin Eberlei added a comment -

(Sort of) Duplicate of DDC-217

Show
Benjamin Eberlei added a comment - (Sort of) Duplicate of DDC-217

People

  • Assignee:
    Benjamin Eberlei
    Reporter:
    Eric Clemmons
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: