Project

General

Profile

Actions

Task #27536

closed

Caching framework db backend: Use own namespace

Added by Christian Kuhn almost 13 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Caching
Target version:
-
Start date:
2011-06-19
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
4.6
PHP Version:
5.3
Tags:
Complexity:
Sprint Focus:

Description

This patch refactores the caching framework database backend in a way that its table layout must not be defined in core and extensions anymore.

This gives us a solution to change the table layout however we want.

The former mandatory 'cacheTable' and 'tagsTable' options are obsolete now, the table names depend on the cache identifier name (which is unique).

All tables are named cachingframework_'identifier' and cachingframework_'identifier'_tags now. They must not be defined in ext_tables.sql anymore and are created by the database backend during flush() (which is called by 'clear-all-cache' for every update since #27506).

This patch is fully backards compatible since the 'old' table namespace of extensions is simply not used anymore. Patches to clean up the system extensions extbase and workspaces will follow.

The changes made it necessary to refactor the database backend unit tests as well, all tests were abstracted a bit more and new tests added.

The layout of needed database tables for cache tables is
handled by the caching framework backend internally:
- Extensions using db backend must not define tables in ext_tables.sql anymore
- Updates to table layouts can be handled by the backend itself
- Defining data and tags table in cacheConfigurations is obsolete
- Cache tables start with 'cachingframework_' and are ignored in install tool
- Table handling is fully backwards compatible


Related issues 6 (0 open6 closed)

Related to TYPO3 Core - Bug #22835: dbbackendtestcase manipulates $GLOBALS['EXEC_TIME'] but doesn't reconstruct original valueClosedChristian Kuhn2010-06-07

Actions
Related to TYPO3 Core - Bug #27671: Caching framework: Reduce code duplication in db backendClosed2011-06-23

Actions
Related to TYPO3 Core - Feature #20500: Change the DB backend to use a default cache tableRejectedChristian Kuhn2009-05-25

Actions
Blocks TYPO3 Core - Bug #27543: Adapt cache configuration to 4.6Closed2011-06-19

Actions
Precedes TYPO3 Core - Bug #25119: performace of cachingframeworkClosed2011-06-202011-06-20

Actions
Precedes TYPO3 Core - Bug #27548: Caching framework db backend: Remove wildcard tag droppingClosed2011-06-212011-06-21

Actions
Actions

Also available in: Atom PDF