RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2025-04-03 13:23:37 +03:00
Code Issues Projects Releases Wiki Activity

Update changelog docs

Browse source
This commit is contained in:
Benjamin Eberlei 2015-01-18 22:52:30 +01:00
parent 79ba8c6be8
commit cd616ff40e
1 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
docs/en/changelog/migration_2_5.rst
View file

@ -86,7 +86,7 @@ Example of defining and using embeddables classes:
} }
/** @Embeddable */ /** @Embeddable */
class Price class Money
{ {
/** @Column(type = "decimal") */ /** @Column(type = "decimal") */
private $value; private $value;
@ -314,13 +314,14 @@ When marking a one-to-many association with ``fetch="EAGER"`` it will now
execute one query less than before and work correctly in combination with execute one query less than before and work correctly in combination with
``indexBy``. ``indexBy``.
Full support for EntityManagerInterface Better support for EntityManagerInterface
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Most of the locations where previously only the ``Doctrine\ORM\EntityManager`` Many of the locations where previously only the ``Doctrine\ORM\EntityManager``
was allowed are now changed to accept the ``EntityManagerInterface`` that was was allowed are now changed to accept the ``EntityManagerInterface`` that was
introduced in 2.4. This allows you to more easily use the decorator pattern introduced in 2.4. This allows you to more easily use the decorator pattern
to extend the EntityManager if you need. to extend the EntityManager if you need. Its still not replaced everywhere,
so you still have to be careful.
DQL Improvements DQL Improvements
~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~
@ -371,7 +372,7 @@ DQL Improvements
Custom DQL Functions: Add support for factories Custom DQL Functions: Add support for factories
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Previoiusly custom DQL functions could only be provided with their Previously custom DQL functions could only be provided with their
full-qualified class-name, preventing runtime configuration through full-qualified class-name, preventing runtime configuration through
dependency injection. dependency injection.