> You cannot use `postFlush` to detect rollbacks, as exceptions causing > rollbacks bubble up, and `postFlush` is never called in those cases. > > See the code directly for reference: > https://github.com/doctrine/doctrine2/blob/20c6bfd360b3db9e9bc53e5ae37afe1a22dccca3/lib/Doctrine/ORM/UnitOfWork.php#L398 > > <https://github.com/doctrine/doctrine2/blob/20c6bfd360b3db9e9bc53e5ae37afe1a22dccca3/lib/Doctrine/ORM/UnitOfWork.php#L398> >
Thanks for the info Marco. I think my issue is that flush is called multiple times inside the single transaction that is rolled back. I guess there isn’t an event handler at the transaction commit level that I could use to handle the entities that were changed by the various flushes inside the transaction? Otherwise I guess we probably have to look at finding a way to limiting ourselves to a single flush per transaction. -- 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.
