Feature #84072

TYPO3 DB caching tables should not be removed by DB compare

Added by Sybille Peters over 2 years ago. Updated almost 2 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Caching
Target version:
-
Start date:
2018-02-27
Due date:
% Done:

0%

PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

To add robustness and easy recoverability from temporary system failures, planned downtimes or configuration errors, I think the basic Caching DB tables (cf_cache_pages etc.) for the Database Backend should never be removed. That way it would be easier to switch back to Database Caching Backend without having to do a DB compare again.

Currently, the DB compare suggests to remove these tables (if something other than the default DB backend is configured). I never do that but an overzealous admin might.

History

#1 Updated by Sybille Peters over 2 years ago

  • Description updated (diff)

#2 Updated by Georg Ringer almost 2 years ago

  • Status changed from New to Rejected

thanks for creating this issue. however I still would like to close this for the following reasons: The tables are never removed automatically but need interaction by an admin/system maintainer. The configuration of caching strategy can only done by file access which means it requires a developer. Both types of persons must know the impact of reconfiguration and db compare.
furthermore the tables can already stay in the DB even if you use a different caching strategy.

Also available in: Atom PDF