[TYPO3-core] RFC #13945: Bug: Missing key on l18n parent in tt_content table

[Ernesto Baschny [cron IT]]

Christian Kuhn schrieb am 05.06.2010 16:04:

> Susanne Moog wrote:
>>>> t3lib_BEfunc::translationCount issues a query like 'SELECT COUNT(*)
>>>> FROM tt_content WHERE l18n_parent=123 AND sys_language_uid!=0 AND
>>>> deleted=0'. EXPLAIN shows no usable key for this type of query.
>>> FYI: Committed _02 to trunk rev. 7308.
>>
>> How about committing this one to 4_3 too, as it leads to a nearly
>> unusable backend if you have lots of content elements (see my thread on
>> the performance list for that)? What do you think?
> 
> Afaik only critical db changes should go to stable releases. That's why
> I didn't commit to 4.3.
> 
> As this is just an additional index without any side-effects (it won't
> be a problem if the index is not added after update), we might be able
> to bend the rules a bit in this case. But this needs Olivers explicit
> approval.

I also agree to ship v4.3 (stable) with that additional index makes
sense. Nobody is forced to use it on a minor upgrade, but the option to
do so is there.

So +1 on adding it to TYPO3_4-3 also. Oli, what do you think?

Cheers,
Ernesto