OK, I tried it out with some simple test cases. It is necessary and sufficient to do a notification at the owning side.
Am Mittwoch, 7. Januar 2015 13:11:54 UTC+1 schrieb Jàπ (Jasper N. Brouwer): > > Forgot a comma here ;) > > That makes sense, if only Collections are always tracked. > > -- > Jasper N. Brouwer > (@jaspernbrouwer) > > > On 7 January 2015 at 13:06:50, Jasper N. Brouwer ([email protected] > <javascript:>) wrote: > > That makes sense if only Collections are always tracked. > > > > So with Many-To-One / One-To-One associations one side / both sides will > hold an Entity, > > not a Collection, and you'll need to notify Doctrine if the property > holding the Entity > > changes. > > > > -- > > Jasper N. Brouwer > > (@jaspernbrouwer) > > > > > > On 7 January 2015 at 12:59:08, Marco Pivetta ([email protected] > <javascript:>) wrote: > > > On 7 January 2015 at 12:53, 'Jasper N. Brouwer' via doctrine-user < > > > [email protected] <javascript:>> wrote: > > > > > > > Correct, no notification is needed on either side of an association. > > > > > > > > PS: I don't have anything at hand to test this, but you do :) Simply > > > > remove the notifications at both sides of an association and change > that > > > > association. If the change is persisted, then you've confirmed that > > > > notification of associations isn't needed > > > > > > > > > Note that this applies to Many-To-Many. In Many-To-One and One-To-One, > you > > > still have to use the tracking policy explicitly when the property is > > > changed. > > > > > > Marco Pivetta > > > > > > http://twitter.com/Ocramius > > > > > > http://ocramius.github.com/ > > > -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
