Feature #15876
closed
Use explicit INNER JOIN instead of cross join
0%
Description
DB resource usage could be reduced if the pi uses explicit INNER JOIN instead of cross join follwed by a filter in the WHERE clause. Currently the search plugin joins different tables by just listing them allin the FROM clause. If the DB doesn't use an optimizer, this means that first all possible combinations of rows from all tables are generated and later filtered according to the WHERE clause. Using explicit JOIN in the FROM clause with a condition significantly reduces the number of combinations that have to be created prior to filtering with the remaining where clause.
The attached diff is against class.tx_indexedsearch.php version 1.15.2.4 as found in the indexed_search extension included in 4.0beta2
(issue imported from #M2953)
Files
Updated by Alexander Opitz about 11 years ago
- Status changed from Accepted to Needs Feedback
- Target version deleted (
0) - TYPO3 Version set to 4.0
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Dmitry Dulepov)
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.