Я не могу понять, почему. Сначала я думал, что это было потому, что это произошло, память прошла 4MB, но я не смог проверить это. Запросы запрашивания) < /li>
< /ul>
запрос: < /p>
Код: Выделить всё
SELECT count(project_reports.id) as aggregate
FROM
`project_reports`
INNER JOIN `project_user_cache` ON `project_reports`.`project_id` = `project_user_cache`.`project_id`
WHERE
`project_user_cache`.`user_id` = 5
AND `project_reports`.`deleted_at` IS NULL;
< /code>
Объясните: < /p>
id select_type table partitions type possible_keys key key_len ref rows filtered Extra
1 SIMPLE project_reports ref project_id,idx_deleted_date,project_reports_project_id_created_by_index idx_deleted_date 5 const 17908 100.00 Using index condition
1 SIMPLE project_user_cache eq_ref idx_user_project_unique,idx_user_id,idx_project_id idx_user_project_unique 16 const,stagingCentralDB.project_reports.project_id 1 100.00 Using where; Using index
< /code>
анализировать: < /p>
-> Aggregate: count(project_reports.id) (cost=26132 rows=1) (actual time=24962..24962 rows=1 loops=1)
-> Nested loop inner join (cost=24341 rows=17908) (actual time=1.5..24953 rows=46385 loops=1)
-> Index lookup on project_reports using idx_deleted_date (deleted_at=NULL), with index condition: (project_reports.deleted_at is null) (cost=5372 rows=17908) (actual time=1.47..24709 rows=66265 loops=1)
-> Filter: (project_reports.project_id = project_user_cache.project_id) (cost=0.959 rows=1) (actual time=0.00335..0.00342 rows=0.7 loops=66265)
-> Single-row covering index lookup on project_user_cache using idx_user_project_unique (user_id=5, project_id=project_reports.project_id) (cost=0.959 rows=1) (actual time=0.00308..0.00311 rows=0.7 loops=66265)
Подробнее здесь: https://stackoverflow.com/questions/797 ... ount-query
Мобильная версия