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

[Ingo Renner]

Ernesto Baschny [cron IT] wrote:

Hi Ernesto,

thanks for taking the time to look into the patch and trying it out!

> Still one issue:
> 
> You change the SQL-definitions of cache_hash and cache_pagesection:

> Executing that in that order will never add the "id" field,

As you figured out yourself this is a known issue with the database 
compare in the install tool, but is not related to this patch. We need 
to fix this of course before releasing 4.3.0 or even 4.3.0alpha1.
I think Stucki wanted to look into this? @Stucki, do you still plan 
doing so?

> So to overcome that problem, I would like to know if there is a need for
> an "auto_increment" field in a caching table? Isn't that unnecessary
> overhead for something that is ought to be fast?

does auto increment slow things down? didn't know if that is the case...

> Apart from that, do we need to re-use the table names "cache_hash" and
> "cache_pagesection" if we are changing their definition completely?
> Maybe those should simply be dropped and some fresh new tables with
> different names could be created? That would also avoid the problem of
> older extensions trying to access "reg1" field in cache_hash table etc.

well, there's never been a clear API anyways and I think it's a little 
late now anyways. Other core devs also gave there ok to break things in 
this case. The advantages completely outweigh the disadvantages I'd say, 
do you agree? Stuff would also break if we'd use new tables...

> Other than that, I did some quick tests, and it seems to be working
> fine! Thanks for your efford and persistence on that front! ;)

is that a (/the still needed) +1?


best
Ingo

-- 
Ingo Renner
TYPO3 Core Developer, Release Manager TYPO3 4.2