[DDC-2015] [GH-437] Fixes PersistentCollection::matching() when collection is not initialize... Created: 07/Sep/12  Updated: 20/Dec/13  Resolved: 17/Sep/12

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

Type: Bug Priority: Major
Reporter: Benjamin Eberlei Assignee: Benjamin Eberlei
Resolution: Fixed Votes: 0
Labels: None


 Description   

This issue is created automatically through a Github pull request on behalf of sroddy:

Url: https://github.com/doctrine/doctrine2/pull/437

Message:

...d and there are NEW entities in the collection.

If you have a PersistentCollection not already initialized and you add something to it and if you call matching() on it, that method doesn't return the elements you have just added even if they match the criteria.

This fixes the behaviour checking for any matching element that is NEW and merging it in the returned ArrayCollection.



 Comments   
Comment by Benjamin Eberlei [ 07/Sep/12 ]

A related Github Pull-Request [GH-437] was closed
https://github.com/doctrine/doctrine2/pull/437

Comment by Doctrine Bot [ 20/Dec/13 ]

A related Github Pull-Request [GH-437] was closed:
https://github.com/doctrine/dbal/pull/437

Generated at Sun Dec 21 15:52:57 UTC 2014 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.