[DDC-1775] Notify strategy listener is not attached for new entities Created: 11/Apr/12  Updated: 07/Jul/12  Resolved: 07/Jul/12

Status: Resolved
Project: Doctrine 2 - ORM
Component/s: ORM
Affects Version/s: 2.2.1
Fix Version/s: 2.2.3
Security Level: All

Type: Bug Priority: Major
Reporter: Oleg Namaka Assignee: Benjamin Eberlei
Resolution: Fixed Votes: 1
Labels: None


New entities with Notify strategy for changes and with GeneratedValue(strategy="AUTO") never get the onPropertyChanged listener attached to them. That happens because of the logic in the UOW::scheduleForInsert($entity) method. The last condition in it "isset($this->entityIdentifiers[$oid])" is never true because the identifier is not set and therefore the code that attaches the PropertyChangedListener in addToIdentityMap is never run.

Comment by Guilherme Blanco [ 23/May/12 ]

This is intentional to me.
According to code and documentation, PropertyChanged is supposed to operate over updates, never over inserts.

I experimented changing the code to also notify about changed during new and the consequences were very drastic. Internally, propertyChanged creates entityChangesets that implies an UPDATE.

Marking ticket as won't fix.

Comment by Oleg Namaka [ 24/May/12 ]

In that case the Notify strategy is partially broken:
Category entity:


 * @ORM\Table(name="category")
 * @ORM\Entity
class Category implements TimestampableInterface
     * Caption
     * @var string $caption
     * @ORM\Column(name="caption", type="text", nullable=true)
    protected $caption;
     * Added At
     * @var \DateTime $addedAt
     * @ORM\Column(name="added_at", type="datetime", nullable=true)
    protected $addedAt;

    public function setCaption($caption)
        if ($this->caption != $caption)  {
            $this->_onPropertyChanged('caption', $this->caption, $caption);
            $this->caption = $caption;
    public function setAddedAt($addedAt)
        $oldValue = $this->addedAt;
		$this->addedAt = $addedAt;
        if ((is_null($oldValue) || ($oldValue->getTimestamp() != $this->addedAt->getTimestamp()))) {
            $this->_onPropertyChanged('addedAt', $oldValue, $this->addedAt);

    protected function _onPropertyChanged($propName, $oldValue, $newValue)
        if ($this->_listeners) {
            /** @var $listener \Doctrine\Common\PropertyChangedListener */
            foreach ($this->_listeners as $listener) {
                $listener->propertyChanged($this, $propName, $oldValue, $newValue);

    public function addPropertyChangedListener(PropertyChangedListener $listener)
        $this->_listeners[] = $listener;

OnFlush event handler:


        foreach ($uow->getScheduledEntityInsertions() as $entity) {
            if ($entity instanceof TimestampableInterface) {
                $entity->setUpdatedAt(new \DateTime('now'));
                $entity->setAddedAt(new \DateTime('now'));
                $uow->recomputeSingleEntityChangeSet($em->getClassMetadata(get_class($entity)), $entity);

Code that uses the entity:

        $cat = new \Entity\Category();
        // @todo this is a workaround until the http://www.doctrine-project.org/jira/browse/DDC-1775 is resolved
        $cat->setCaption('Please explain');

If there is no explicit call to the addPropertyChangedListener method, the caption field gets saved but the $addedAt remains null after flush. The entity does not have the attached listener so UnitOfWork does not know anything about the update that happened in the OnFlush event, and the recomputeSingleEntityChangeSet method skips entities with Notify strategy.

Comment by Benjamin Eberlei [ 27/May/12 ]

Changing computeScheduleInsertsChangeSets() would solve this, but it would also mean that the notifier gets injected more than once.

    private function computeScheduleInsertsChangeSets()
        foreach ($this->entityInsertions as $entity) {
            $class = $this->em->getClassMetadata(get_class($entity));

            $this->computeChangeSet($class, $entity);

            if ($entity instanceof NotifyPropertyChanged) {

I think injecting in scheduleForInsert() is ok, but we have to look at potential problems also

Comment by Benjamin Eberlei [ 07/Jul/12 ]


Generated at Wed Sep 02 13:03:38 EDT 2015 using JIRA 6.4.10#64025-sha1:5b8b74079161cd76a20ab66dda52747ee6701bd6.