PersistentCollection::removeElement with fetch EXTRA_LAZY remove from DB without persist&flush

[karakum]

Bug Report

Q	A
BC Break	yes/no
Version	2.6.3

Summary

This code was added a long-long ago in 2011 year...
356f587#r33750844

Current behavior

$collection->removeElement($el) execute sql DELETE before(without) $em->persist()&$em->flush().

How to reproduce

1 Many-to-many collection with fetch="EXTRA_LAZY"
2 Remove element from collection

Expected behavior

There must no DB changes be made without $em->persist()&$em->flush()

[lcobucci]

@karakum changes might still happen without $em->persist(), depending on the tracking policy. However, $em->flush() is a must. Would you be able to send us a functional test reproducing this issue? It would be quite helpful 👍

[lcobucci]

@karakum never mind my comment, this is apparently the way things are designed to work (TIL!)

[karakum]

@lcobucci could you please give me doc-link about this "feature"?

[lcobucci]

@karakum unfortunately, there's just no documentation for that: #7765

Changing this is a BC break but I believe we have to find a solution to overcome what @guilhermeblanco mentioned in the commit and still make this managed by the UoW.