Doctrine 2 - ORM
  1. Doctrine 2 - ORM
  2. DDC-1279

Shouldn't Cached Results Trigger LifeCycleEvents?

    Details

    • Type: Improvement Improvement
    • Status: 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

          Activity

          Hide
          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
          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
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: