Commit order reversed? #7210

New Issue

admin · 2026-01-22T15:47:02+01:00

admin commented

2026-01-22 15:47:02 +01:00

Originally created by @olivier1980 on GitHub (Aug 9, 2023).

Since release v2.16 this line of code won't save the entities in order of the loop anymore:

 foreach ($importDossier->getKlanten() as $klant) {
          $klant->setIsActive(true);
          $this->entityManager->persist($klant);
}

The last line to be executed will get an earlier id in the DB than the first iteration of the loop...which seems weird. Is this expected behaviour?

I noticed work was done on the commit order here: https://github.com/doctrine/orm/pull/10547

Originally created by @olivier1980 on GitHub (Aug 9, 2023). Since release v2.16 this line of code won't save the entities in order of the loop anymore: ``` foreach ($importDossier->getKlanten() as $klant) { $klant->setIsActive(true); $this->entityManager->persist($klant); } ``` The last line to be executed will get an earlier id in the DB than the first iteration of the loop...which seems weird. Is this expected behaviour? I noticed work was done on the commit order here: https://github.com/doctrine/orm/pull/10547

admin closed this issue

2026-01-22 15:47:03 +01:00

admin commented

2026-01-22 15:47:04 +01:00

@olivier1980 commented on GitHub (Aug 9, 2023):

Apparently this is now the new behaviour:

    Do not make any assumptions in your code about the number of queries
    it takes to flush changes, about the ordering of ``INSERT``, ``UPDATE``
    and ``DELETE`` queries or the order in which entities will be processed.

and they don't consider it a BC breaking change lol

@olivier1980 commented on GitHub (Aug 9, 2023): Apparently this is now the new behaviour: ``` Do not make any assumptions in your code about the number of queries it takes to flush changes, about the ordering of ``INSERT``, ``UPDATE`` and ``DELETE`` queries or the order in which entities will be processed. ``` and they don't consider it a BC breaking change lol

admin commented

2026-01-22 15:47:04 +01:00

@greg0ire commented on GitHub (Aug 9, 2023):

Damn right we don't! And the paragraph you're quoting does not document new behavior. It merely newly documents that using the ORM does not and never did guarantee any particular insertion order.

@greg0ire commented on GitHub (Aug 9, 2023): Damn right we don't! And the paragraph you're quoting does not document new behavior. It merely newly documents that using the ORM does not and never did guarantee any particular insertion order.

admin commented

2026-01-22 15:47:04 +01:00

@derrabus commented on GitHub (Aug 10, 2023):

FTR, duplicate of #10864

@derrabus commented on GitHub (Aug 10, 2023): FTR, duplicate of #10864

admin referenced this issue

2026-01-22 16:07:20 +01:00

[PR #7210] Further exceptions tweaks #10372

Sign in to join this conversation.