[TYPO3-core] FYI: Fixed bug #12835: Caching error when clearing indexed search elements in info module

[Martin Kutschker]

Steffen Kamper schrieb:
> Hi Masi,
> 
> Martin Kutschker schrieb:
>> Steffen Kamper schrieb:
>>> Hi Masi,
>>>
>>> Martin Kutschker schrieb:
>>>> Oliver Hader schrieb:
>>>>> The following changes were committed to SVN Trunk (rev. 6593)
>>>>>
>>>>> Solution:
>>>>> Integrate a proper check to use the caching framework or the standard
>>>>> caching.
>>>> I hope that the multitude of checks is worth the speed. Doesn't seem
>>>> to be easy to maintain.
>>>>
>>> the drawback of having 2 cache-systems.
>>
>> Forget it. There are other (IMHO better) ways to handle to systems,
>> but they again introduce
>> objects. And it seems to me that Rupi wanted to get rid of them.
>>
> that was exact the reason to get the performance improved.

The net result is code with 2 design strategies. The switch-strategy defeats the whole purpose of
the caching framework. Maybe the framework isn't flexible enough to support the old tables, but in a
clean design I should only need to get a cache object. Now I have to fiddle with switches.

The snippet tells me that the caching framework has a problem that it is too general. I have to loop
over tags. Or maybe it is only that TYPO3 lacks a page-cache-object. This one should have a
clearCache($pidList) method.

The only switch would be the one that creates either a page-cache object built around the caching
framework or one using the old-style table. That would remove hard-coded delete statements in
extensions (they should not need to know about the structure of the cache tables).

Masi