> > > > > > 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. > > > > > > > > > Well, ANALYZE has changed something. Now query is using PRIMARY KEY and > > executing almost instantly :-) > > > > Please post the results of: > > SELECT * FROM sqlite_stat1; > >
Sure, tbl = T idx = stat = 1 tbl = item idx = idxitem_name_value stat = 21 7 1 tbl = log idx = idxlog_kind_computer_process_who_id_msg_created_at stat = 2815667 563134 563134 469278 74097 1 1 1 tbl = log idx = idxlog_kind_computer_process_id_who_msg_created_at stat = 2815667 563134 563134 469278 1 1 1 1 tbl = log idx = idxlog_kind_computer_id_process_who_msg_created_at stat = 2815667 563134 563134 1 1 1 1 1 tbl = log idx = idxlog_kind_id_computer_process_who_msg_created_at stat = 2815667 563134 1 1 1 1 1 1 tbl = log idx = idxlog_kind_computer_process_who_msg_created_at stat = 2815667 563134 563134 469278 74097 2 2 tbl = log idx = idxlog_created_at stat = 2815667 106 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
