Hello,

I'd like to know if the management of multiple indexes
on select statement is in the TODO list of SQLite?

On joined request, this lack is a real performance killer.

Example:
select t1.id,t2.name
from t1,t2
where t1.id IN(a00,b00, ....,z99) and t1.t2id = t2.id;

For now, SQLite use by default the wrong index and make
a full join ignoring the 'IN' restriction. I need
to force the index selection like this to gain a little
speed:

select t1.id,t2.name
from t1,t2
where t1.id IN(a00,b00, ....,z99) and +t1.t2id = t2.id;

Once rows from t1 are selected (fast with the forced index),
SQLite does not use the t2 index on 'id' to speed up the join.
In my case, t2 is quite big.

The only "solution" i see could be to split the request in two
to use indexes on both tables...
Can anyone advise me?

Thanks. Bye,
--
Guillaume FOUGNIES

Reply via email to