Add UPGRADE note
This commit is contained in:
parent
a04113f410
commit
f52a512c59
16
UPGRADE.md
16
UPGRADE.md
@ -1,18 +1,24 @@
|
||||
# Upgrade to 2.5
|
||||
|
||||
## Minor BC BREAK: EntityPersister `exists` now supports Criteria object
|
||||
|
||||
As of 2.5, `EntityPersister` interface supports a Criteria object as the `extraConditions` params. It
|
||||
was previously typehinted to be an array, so if you implement your own persister, you need to modify
|
||||
the signature.
|
||||
|
||||
## Minor BC BREAK: Custom Hydrators API change
|
||||
|
||||
As of 2.5, `AbstractHydrator` does not enforce the usage of cache as part of
|
||||
As of 2.5, `AbstractHydrator` does not enforce the usage of cache as part of
|
||||
API, and now provides you a clean API for column information through the method
|
||||
`hydrateColumnInfo($column)`.
|
||||
Cache variable being passed around by reference is no longer needed since
|
||||
Cache variable being passed around by reference is no longer needed since
|
||||
Hydrators are per query instantiated since Doctrine 2.4.
|
||||
|
||||
## Minor BC BREAK: Entity based ``EntityManager#clear()`` calls follow cascade detach
|
||||
|
||||
Whenever ``EntityManager#clear()`` method gets called with a given entity class
|
||||
name, until 2.4, it was only detaching the specific requested entity.
|
||||
As of 2.5, ``EntityManager`` will follow configured cascades, providing a better
|
||||
Whenever ``EntityManager#clear()`` method gets called with a given entity class
|
||||
name, until 2.4, it was only detaching the specific requested entity.
|
||||
As of 2.5, ``EntityManager`` will follow configured cascades, providing a better
|
||||
memory management since associations will be garbage collected, optimizing
|
||||
resources consumption on long running jobs.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user