http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DDC-54 Doctrine 2 - ORM <p>Currently the postLoad events and callbacks are triggered after the entity has been created and filled with its "primitive" state but before associations are available. The postLoad events and callbacks should be postponed so that they are triggered after associations have been initialized.</p> DDC-54

Trigger postLoad events and callbacks after associations have been initialized

Improvement Major In Progress Unresolved All Benjamin Eberlei Roman S. Borschel Thu, 15 Oct 2009 18:34:38 +0000 Thu, 11 Oct 2012 10:37:46 +0000 2.0-ALPHA2 2.x ORM 6 6 <p>If this is to be included in 2.0 it needs to happen for RC1. However, it is not clear yet whether it will be done in time.</p> <p>How would you solve this Roman? I thought of adding a query hint so that the postLoad inside unit of work is not triggered and gathering all the entities that have a post load event in an array inside the object hydrator, then iterating it after taking the snapshots of all collections inside hydrateAll</p> <p>@Benjamin: Not sure what you would use the query hint for but in general that is the approach I had in mind, yes. You can't get around iterating over the entities after the actual hydration.</p> <p>The query hint would do something like:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> <span class="code-comment">//TODO: These should be invoked later, after hydration, because associations may not yet be loaded here. </span> <span class="code-keyword">if</span> (isset($class-&gt;lifecycleCallbacks[Events::postLoad]) &amp;&amp; !isset($hints['hydrationPostLoad'])) { $class-&gt;invokeLifecycleCallbacks(Events::postLoad, $entity); } <span class="code-keyword">if</span> ($<span class="code-keyword">this</span>-&gt;evm-&gt;hasListeners(Events::postLoad) &amp;&amp; !isset($hints['hydrationPostLoad'])) { $<span class="code-keyword">this</span>-&gt;evm-&gt;dispatchEvent(Events::postLoad, <span class="code-keyword">new</span> LifecycleEventArgs($entity, $<span class="code-keyword">this</span>-&gt;em)); } </pre> </div></div> <p>another way would be to move that code out of UoW::createEntity completly and have the persisters call it when they use that method.</p> <p>Leaving that code in UoW does not make sense to me, if it is moved, it needs to be moved completely. Why do you think the persisters should do it? Initially I thought collecting the affected entities during hydration and then when hydration is done iterating over them and triggering the postLoad events.</p> <p>Yes but postLoad has to be triggered for non Hydrated entities (i.e. Persister) also</p> <p>Moved back</p> <p>Hi Gyus, I need access to associations in postLoad or similar event, and my idea is to dispatch new event after full initialisation of object, what do You think about it? If I can help please let me know <img class="emoticon" src="http://www.doctrine-project.org/jira/images/icons/emoticons/smile.gif" height="20" width="20" align="absmiddle" alt="" border="0"/> It's important for me.</p> <p>Now in my PostLoad access to associations is work fine. Why this issue is still in Unresolved status?</p> <p>What do you (Roman and Benjamin) think about adding postHydrate event which would be called within ObjectHydrator::hydrateAllData() on every entity collected during hydration? I could prepare a patch for this. I personally think this would be better than adding a hint that changes behaviour of postLoad event.</p>