New entities don't have/need a change set: the entire entity is the change set...
Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On 28 July 2015 at 14:07, Thomas Baumann <[email protected]> wrote: > Hi There, > > A colleague and me ask ourselves how to efficiently compute change sets > for new entities during the onFlush event. To notify the uow about updates, > we can use UnitOfWork::propertyChanged() safely, but what about new > entities? We found the methods computeChangeSet() and > recomputeSingleEntityChangeSet(), that both seem to do the job for only one > entity, but both methods are marked as internal, so we should not use > those, right? > > We can achieve the entities to be recognised by the uow by > calling computeChangeSets(), but this is calculating all change sets again > and again, as we see it. Basically we only need the changes of one entity > to be computed. > > How to achieve this efficiently without breaking the "do not call > internals" rule? > > Any ideas, experiences with that? > > Best, > Thomas > > -- > 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. > -- 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.
