Feature #16667
closed
Database keys
0%
Description
IMHO fields like deleted, hidden, sys_language_uid,. l18n_parent,sorting should be database indices by default for performance reasons.
(issue imported from #M4431)
Updated by Dmitry Dulepov about 18 years ago
"IMHO" is not a patch and not enough for any practical work. Database indexes is a complex thing and simply including all these fields to index will not work. If you have any real proposal, please, post them. Otherwise this bug report can be closed...
Updated by Nikolas Hagelstein about 18 years ago
At least deleted and hidden are fields rapitly used within where clauses.
Having them in a e.g Left join clause without beeing indexed dramiticly raises the query s runtime. (e.g left join on x.uid=y.uid and y.hidden=0).
Even if T3 itself does'nt make use of joins internally that much it might make senses anyway.
Regarding the I18l fields: having a huge amount of translation records makes it impossible to follow the T3 philisophie of fetching the default language and fetching the translation by fireing a second query. Therefor such a situation has to be solved by using complex joins for performance reason. In this scenarion the above named fields need to be indices (see left join example)
"Database indexes is a complex thing and simply including all these fields to index will not work."
For what reasons? Could you please explain?
Updated by Dmitry Dulepov almost 13 years ago
- Status changed from New to Resolved
- Target version deleted (
0) - TYPO3 Version changed from 4.0 to 4.6
- PHP Version deleted (
4)
That was resolved finally in 4.6.
Updated by