> > > Database extension is ".dblite" > > That should be okay. No need to change that. > > Something that might speed up your operation is to issue the SQL command > 'ANALYZE' just once. The results are stored in the database file, so you can > just do it manually now you have some data in the database. It gives the > query optimizers lots of clues about how best to optimize each query. So do > an ANALYZE, then close the database and do your timing tests again.
Okay, will do that. > > If you're still getting strange results after that, you can use the > command-line tool to make SQLite reveal whether it's using an index or not. > You do that by issuing your SELECT command with 'EXPLAIN QUERY PLAN ' at the > beginning of it: > > EXPLAIN QUERY PLAN SELECT 1 as today, id as rowid, > kind,who,msg,computer,process,created_at,id FROM log WHERE id > 4070636 AND > id <= 9223372036854775807 AND kind = 'info' AND computer='KRAFTWAY'; > > Looking at the output it produces (which you may post, by all means) any > mention of 'scan' means it's having to read every record in the database, > whereas a mention of an index means it's using an index as expected. > You missed it in my post - I did it. I did "EXPLAIN ..." and SQLITE says it's using covering index. There's nohting wrong in the query plan. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
