iteration risk note

> instead of loading the whole result into memory at once
is not the full truth.

There is a certain risk of processes getting killed due to memory allocation with large iteration. This is caused by result buffering of the client not being visible to PHP and thus not from 'within' the process.

It is not certain that this occurs with all database clients but seems rather likely to at this point.

This is only a proposal for discussion as I am not certain how to best add the information or if to add it at all (was it obvious before?). Personally I got confused by the existing description and didn't notice the memory implication until further investigation using `top` reported the process to run at 3+GB memory while PHP reported 400M real peak usage.
makes doctrine less dependent upon the symfony yamp component
allow passing EntityManagerInterface when creating a HelperSet
stop executing executeDeletions when there is nothing to to delete anymore
Allow if parameter exists in SQLFilter
Failing Test (since commit 53a5a48aed7d87aa1533c0bcbd72e41b686527d8)

Hi,

It seems to be a regression since the commit https://github.com/doctrine/doctrine2/commit/53a5a48aed7d87aa1533c0bcbd72e41b686527d8

Doctrine\ORM\PersistentCollection can be populated in $changeSet if you set a PreUpdate and PostUpdate event.

Original issue: http://www.doctrine-project.org/jira/browse/DDC-3033
Update DDC3033Test.php
Update DDC3033Test.php
Use boolean values for 'unique' attribute

As defined in: https://github.com/doctrine/doctrine2/blob/master/doctrine-mapping.xsd#L294

Same as 'nullable' attribute. 

It was being exported as a "1" for TRUE and "0" for false
Added test to ensure boolean metadata is properly exported/serialized to XML
[DDC-3045] Check that EntityRepository APIs prevent SQL injection through field names. Improve EntityManager#find() error handling when invalid identifier fields are passed.
Merge branch 'DDC-3045'
Merge pull request #984 from holtkamp/patch-1

Use boolean values for 'unique' attribute
[DDC-3033] Fix bug in UnitOfWork#recomputeSingleEntityChangeSet.

The fix for DDC-2624 had a side effect on recomputation of
changesets in preUpdate events. The method wasn't adjusted
to the changes in its sister method computeChangeSet() and
had wrong assumptions about the computation.

Especially:
1. Collections have to be skipped
2. Comparison was changed to strict equality only.
[DDC-3033] Clarify restrictions in events.
Merge branch 'DDC-3033'
[DDC-2996] Fix bug in UnitOfWork#recomputeSingleEntityChangeSet

When calling UnitOfWork#recomputeSingleEntityChangeSet on an entity
that didn't have a changeset before, the computation was ignored.
This method however is suggested to be used in "onFlush" and "preFlush"
events in the documentation.

Also fix a bug where recomputeSingleEntityChangeSet was used
before calculating a real changeset for an object.
Merge branch 'DDC-2996'
[DDC-3018] Fix string literals in new operator.
Merge branch 'DDC-3018'