[TYPO3-dev] How standard compliant is "truncate"?

Steffen Kamper info at sk-typo3.de
Thu Feb 5 17:21:56 CET 2009


Dmitry Dulepov schrieb:
> Hi!
> 
> Peter Kuehn [wmdb] wrote:
>> maybe it helps if i resort the last two posts a bit:
>>
>>> TYPO3 does not use referral integrity
>>>> If there are no FOREIGN KEY constraints,
>>>> InnoDB performs fast truncation by dropping the original table and
>>>> creating an empty one with the same definition, which is much faster
>>>> than deleting rows one by one
>> ... see? ;)
> 
> No :( Do you mind explaining? :)
> 

he mean "If there are _no_ FOREIGN KEY constraints,

so InnoBD does the fast truncation for us (TYPO3) ;)

that's also my expierience, as the cache tables are InnoDB and truncate 
is really fast on them.

vg Steffen




More information about the TYPO3-dev mailing list