adds a new output format
[DDC-93] Started ValueObjectsTest
[DDC-93] Parse @Embedded and @Embeddable during SchemaTool processing to make parsing work.
[DDC-93] Implement first working version of value objects using a ReflectionProxy object, bypassing changes to UnitOfWork, Persisters and Hydrators.
[DDC-93] Add some TODOs in code.
[DDC-93] Show CRUD with value objects with current change tracking assumptions.
[DDC-93] Rename ReflectionProxy to ReflectionEmbeddedProperty, Add DQL test with Object and Array Hydration.
add shortcut for force
Cleaned up documentation

Cleaned up documentation, tweaked some of the grammar, changed class#method() references to class::method(), added warning about performance impact of lazy loading
Updated method documentation to use # for instance methods instead of ::
Update getting-started.rst

Replaced ``class::$field`` with ``class#field`` to match Doctrine style

Cleaned up three paragraphs mentioned in https://github.com/doctrine/doctrine2/pull/734
Update DDC719Test.php to be compatible with MsSQL

Apparently Doctrine adds "with (nolock)" now for the mssql platform, but the test has not been updated yet.
Update DatabaseDriverTest.php

SQL Server does not support unsigned integers
A nicer way of detecting the platform

Inspired by https://github.com/doctrine/doctrine2/blob/master/tests/Doctrine/Tests/ORM/Functional/DatabaseDriverTest.php#L188
Implemented "contains" operator for Criteria expressions
[DDC-2668] Fix trim leading zero string
Improved error messages in Paginator: LimitSubqueryOutputWalker

The already existing follow-up check throwing "Not all identifier properties can be found in the ResultSetMapping: %s" is a much more technical description.

If $sqlIdentifier is empty (count 0) it can be concluded that there are no mapped results. An alternative error message could thus be "The Paginator does not support queries without mapped results." (line 153).

Possibly '!=' on line 154 could be replaced by '>' because i think this is the only situation that can occur. But since i don't know this for sure, i left it like i found it.
Improved error messages in Paginator: LimitSubqueryOutputWalker



The already existing follow-up check throwing "Not all identifier properties can be found in the ResultSetMapping: %s" is a much more technical description.

If $sqlIdentifier is empty (count 0) it can be concluded that there are no mapped results. An alternative error message could thus be "The Paginator does not support queries without mapped results." (line 153).

Possibly '!=' on line 154 could be replaced by '>' because i think this is the only situation that can occur. But since i don't know this for sure, i left it like i found it.

Didn't use elseif in this commit as per Stof his suggestion.
Multiple invokation of listeners on PreFlush event

Only lifecycle callbacks and entity listeners should be triggered here. The preFlush listener event is already triggered at the beginning of commit()
Added unit test