[TYPO3-mvc] [!!!] FYI: Changes of Extbase in TYPO3 beta3
Jochen Rau
jochen.rau at typoplanet.de
Sat Nov 7 16:24:12 CET 2009
Hi.
There are some changes introduced with v0.9.13 of Extbase (=beta3 of
TYPO3 4.3).
1) Lazy Loading
The configuration of the loading strategy has changed. The TCA option
"loadingStrategy" was removed. You have to annotate your property with
"@lazy" now (compatible with FLOW3). Extbase chooses the appropriate
strategy depending on the property type:
ObjectStorage ==> LazyObjectStorage
Tx_MyExt_MyObject ==> LazyLoadingProxy
2) Cascading Deletions
Related objects are not deleted with its parent by default. There are
two ways to get them deleted with its parent:
You can remove them "manually" from their repository (if any),
or you can annotate the parent property with "@cascade remove".
The relation information keeps intact if they are marked as deleted=1.
This is only useful if we have a one-to-one-relation or
one-to-many-relation. Many-to-many-relations are not touched.
Keep in mind, that detaching an object from its parent will remove the
relation but not the related object.
3) Reference Index and Cache Clearing
The reference index is not updated by default anymore for performance
reasons. You have to set:
config.tx_extbase.persistence.updateReferenceIndex = 1
to enable this feature.
There is also an option
config.tx_extbase.persistence.enableAutomaticCacheClearing = 1
which is enabled by default. Setting this to 0 can increase the performance.
We really appreciate your feedback.
Regards
Jochen
--
Every nit picked is a bug fixed
More information about the TYPO3-project-typo3v4mvc
mailing list