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

[Peter Kuehn [wmdb]]

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? ;)



Dmitry Dulepov schrieb:
> Hi!
> 
> ries van Twisk wrote:
>> For an InnoDB table before version 5.0.3, InnoDB processes TRUNCATE
>> TABLE by deleting rows one by one. As of MySQL 5.0.3, row by row
>> deletion is used only if there are any FOREIGN KEY constraints that
>> reference the table. 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
> 
> How does it contradict my words in regard to TYPO3? TYPO3 does not use referral integrity, so for TYPO3 TRUNCATE is equivalent to DELETE on InnoDB.
>