> > 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 :-) _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
- [sqlite] SELECT query first run is V... Григорий Григоренко
- Re: [sqlite] SELECT query first... Max Vlasov
- Re: [sqlite] SELECT query f... Григорий Григоренко
- Re: [sqlite] SELECT query f... Simon Slavin
- Re: [sqlite] SELECT que... Григорий Григоренко
- Re: [sqlite] SELECT... Max Vlasov
- Re: [sqlite] S... Max Vlasov
- Re: [sqlite] SELECT... Simon Slavin
- Re: [sqlite] S... Григорий Григоренко
- Re: [sqlite] S... Григорий Григоренко
- Re: [sqlit... Richard Hipp
- Re: [sqlit... Григорий Григоренко
- Re: [sqlite] SELECT... Григорий Григоренко
- Re: [sqlite] S... Max Vlasov
- Re: [sqlite] SELECT... Григорий Григоренко
- Re: [sqlite] S... Richard Hipp
- Re: [sqlite] SELECT que... Max Vlasov
- Re: [sqlite] SELECT query first... Black, Michael (IS)
- Re: [sqlite] SELECT query f... Григорий Григоренко
- Re: [sqlite] SELECT que... Simon Slavin