Home/ Questions/Q 7007533
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T21:37:10+00:00

I’m using this kind of queries with different parameters : EXPLAIN SELECT SQL_NO_CACHE `ilan_genel`.`id`

  • 0

I’m using this kind of queries with different parameters :

EXPLAIN SELECT SQL_NO_CACHE `ilan_genel`.`id` , `ilan_genel`.`durum` , `ilan_genel`.`kategori` , `ilan_genel`.`tip` , `ilan_genel`.`ozellik` , `ilan_genel`.`m2` , `ilan_genel`.`fiyat` , `ilan_genel`.`baslik` , `ilan_genel`.`ilce` , `ilan_genel`.`parabirimi` , `ilan_genel`.`tarih` , `kgsim_mahalleler`.`isim` AS mahalle, `kgsim_ilceler`.`isim` AS ilce, (

SELECT `ilanresimler`.`resimlink`
FROM `ilanresimler`
WHERE `ilanresimler`.`ilanid` = `ilan_genel`.`id`
LIMIT 1
) AS resim
FROM (
`ilan_genel`
)
LEFT JOIN `kgsim_ilceler` ON `kgsim_ilceler`.`id` = `ilan_genel`.`ilce`
LEFT JOIN `kgsim_mahalleler` ON `kgsim_mahalleler`.`id` = `ilan_genel`.`mahalle`
WHERE `ilan_genel`.`ilce` = '703'
AND `ilan_genel`.`durum` = '1'
AND `ilan_genel`.`kategori` = '1'
AND `ilan_genel`.`tip` = '9'
ORDER BY `ilan_genel`.`id` DESC
LIMIT 225 , 15

and this is what i get in explain section:

explain

these are the indexes that i already tried to use:

indexes

any help will be deeply appreciated what kind of index will be the best option or should i use another table structure ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should first simplify your query to understand your problem better. As it appears your problem is constrained to the ilan_gen1 table, the following query would also show you the same symptoms.:

    SELECT * from ilan_gene1 WHERE `ilan_genel`.`ilce` = '703'
AND `ilan_genel`.`durum` = '1'
AND `ilan_genel`.`kategori` = '1'
AND `ilan_genel`.`tip` = '9'

    So the first thing to do is check that this is the case. If so, the simpler question is simply why does this query require a file sort on 3661 rows. Now the ‘hepsi’ index sort order is:

    ilce->mahelle->durum->kategori->tip->ozelik

    I’ve written it that way to emphasise that it is first sorted on ‘ilce’, then ‘mahelle’, then ‘durum’, etc. Note that your query does not specify the ‘mahelle’ value. So the best the index can do is lookup on ‘ilce’. Now I don’t know the heuristics of your data, but the next logical step in debugging this would be:

    SELECT * from ilan_gene1 WHERE `ilan_genel`.`ilce` = '703'`

    Does this return 3661 rows?

    If so, you should be able to see what is happening. The database is using the hepsi index, to the best of it’s ability, getting 3661 rows back then sorting those rows in order to eliminate values according to the other criteria (i.e. ‘durum’, ‘kategori’, ‘tip’).

    The key point here is that if data is sorted by A, B, C in that order and B is not specified, then the best logical thing that can be done is: first a look up on A then a filter on the remaining values against C. In this case, that filter is performed via a file sort.

    Possible solutions

    1. Supply ‘mahelle’ (B) in your query.
    2. Add a new index on ‘ilan_gene1’ that doesn’t require ‘mahelle’, i.e. A->C->D…

    Another tip

    In case I have misdiagnosed your problem (easy to do when I don’t have your system to test against), the important thing here is the approach to solving the problem. In particular, how to break a complicated query into a simpler query that produces the same behaviour, until you get to a very simple SELECT statement that demonstrates the problem. At this point, the answer is usually much clearer.

    • 0