Broken commit order in 2.6 #7259
Description
BC Break Report
| Q | A |
|---|---|
| BC Break | yes |
| Version | 2.6 |
Summary
Commit order is wrong in some cases, leading to broken inserts (inserting without the id for the foreign key). this is dependant on the order of persist() calls.
Previous behavior
Flushing was working fine
Current behavior
Flush is failing by trying to insert NULL in a non-nullable foreign key (probably planning to update the field later).
How to reproduce
See #7260 which provides some tests reproducing the issue.