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

[Dmitry Dulepov]

Hi!

Peter Kuehn [wmdb] wrote:
> Youve closed the core related ticket
> http://bugs.typo3.org/view.php?id=5370 containing the clear statement "I
> have seen a TYPO3 website go down completely, because of cleaning the
> cache or updating the TS code.", which i can definately confirm, since
> we had the same worst case scenario more than once, with the final note
> "Closing the issue because it is no longer relevant".

Please, reread the issue subject and text, not the comment. If the comment goes offtopic, it is a problem of the comment. We do not fix comments, we fix the problem described in the text of the report. It says to use TRUNCATE instead of DELETE. This is what we do in 4.3. Therefore original issue is no longer relevant. The original issue does not exist anymore. If you have another issue, create another bug report.

What would you propose? Not to clear cache?

> From my point of view, its no less then a maximum credible accident if
> an application is able to shutdown an in production server by point and
> click and definately anything but "not relevant".
> 
> Im sure, at least I hope, that I misunderstood you somehow.

You did :) Deom developer's view there should be one report for one issue. For example, if issue is "Change DELETE to TRUNCATE", than "DELETE or TRUNCATE kills my server" is a completely different issue and it should be failed separately.

-- 
Dmitry Dulepov
TYPO3 core team
"Sometimes they go bad. No one knows why" (Cameron, TSCC, "Dungeons&Dragons")