[PR #1531] fixed outdated entity #9589

New Issue

admin · 2026-01-22T16:04:46+01:00

admin commented

2026-01-22 16:04:46 +01:00

Original Pull Request: https://github.com/doctrine/orm/pull/1531

State: closed
Merged: No

I found an issue with outdated entities. If you have following code which will be called by your request:

$em->beginTransaction();
try {
    $repository = $em->getRepository(Entity::class);
    /** @var Entity $entity */
    $entity = $repository->findOneBy(['tyef' => 'foo']);
    $em->lock($entity, LockMode::PESSIMISTIC_WRITE);
    $entity->increase(1); //increase field 'bar'

    sleep(2);

    $em->persist($entity);

    $em->flush();
    $em->commit();
} catch (\Exception $e) {
    $em->rollback();
    throw $e;
}

This will happen:

Before requests: Number is 30 (in fieldbar)
Request 1 is fired
Request 2 is fired
Request 1 finished. Number is 31
Request 2 finished. Number is 31

Since we have a write lock inside of a transaction I expect to have 32. The entity is not up to date and has do be refreshed. If you use the EntityRepository::find() method with the write lock it works fine. It only occurs if you add the lock afterwards.

**Original Pull Request:** https://github.com/doctrine/orm/pull/1531 **State:** closed **Merged:** No --- I found an issue with outdated entities. If you have following code which will be called by your request: ``` $em->beginTransaction(); try { $repository = $em->getRepository(Entity::class); /** @var Entity $entity */ $entity = $repository->findOneBy(['tyef' => 'foo']); $em->lock($entity, LockMode::PESSIMISTIC_WRITE); $entity->increase(1); //increase field 'bar' sleep(2); $em->persist($entity); $em->flush(); $em->commit(); } catch (\Exception $e) { $em->rollback(); throw $e; } ``` This will happen: 1. Before requests: Number is 30 (in field`bar`) 2. Request 1 is fired 3. Request 2 is fired 4. Request 1 finished. Number is 31 5. Request 2 finished. Number is **31** Since we have a write lock inside of a transaction I expect to have **32**. The entity is not up to date and has do be refreshed. If you use the `EntityRepository::find()` method with the write lock it works fine. It only occurs if you add the lock afterwards.

admin added the pull-request label 2026-01-22 16:04:46 +01:00

admin referenced this issue

2026-01-22 16:11:43 +01:00

[PR #9589] Fix type errors with XML export on PHP 8.1 #11722

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: doctrine/archived-orm#9589