[TYPO3-mvc] deleteAll : none of the foreign table rows are marked as deleted

Julian Kleinhans jk at marketing-factory.de
Wed Jul 22 11:18:00 CEST 2009


Hi Jochen,


Jochen Rau schrieb:
> Hi Matthias.
> 
> Mathias Schreiber [wmdb >] wrote:
>> Jochen Rau schrieb:
>>> In short: there is no general rule for deleting associated instances
>>> other than deleting ValueObjects is always safe.
>>
>> In case of 1:1 and uni-directional 1:n it does know about this.
>> Maybe this can be implemented this way with some sort of config-switch.
> 
> Nope. The given example illustrates a 1:n case as an Employee is 
> normally assignet to only one Department.
> 
> I propose (at least for TYPO3 4.3) to let the extension developer 
> implement this by hand as there is no common solution in FLOW3 either. 
> In 4.4 we could introduce a configuration option.


Sorry, i don't mean an automatical mechanism!
It's right that it must implement by hand and you do that in the blog 
repository. And there is the bug!

But you are right, there is already a known bug
http://forge.typo3.org/issues/show/3875

regards
julian


> 
> Regards
> Jochen
> 
> 


More information about the TYPO3-project-typo3v4mvc mailing list