[TYPO3-core] RFC #9505: Make the caches in TYPO3 use the new caching framework

[Martin Kutschker]

Ingo Renner schrieb:
>>> I am sure it "slows down" something, but I cannot imagine that it is
>>> noticeable. But as we already have seen two negative side effects
>>> (update problem and potential slow-down) of the "id" auto_increment
>>> field, and no useful function for that field (?), we might as well drop
>>> it. Any reason against it?
>>
>> If we don't need it, drop it.
> 
> AFAIK we at least need it as a fast index (numeric/autoincrement)
> indexes should be faster than having a string index mysql needs to work
> through.

I have heard that numeric indices aren't faster than string indices.

>> To make things easier I think we should simply use new tables. It saves
>> us from adding IMHO superfluous stuff to the installer (the change is
>> far from being a standard change). As any old will break anyway with the
>> new table layout we can simply create a new one and discard the old.
> 
> no, why? It's working!

Because you cannot update the database easily? I doubt that you'll be
able to make the installer/EM change the table layout properly. Again
the tasks to get it right:

* clear table - wouldn't work otherwise!
* add field without auto_increment
* add key
* add field with auto_increment

This is way to complicated to code. Using a new table is no work at all
and will work out-of-the-box.

Masi