Cole, thanks for your help. > I doubt that you will. They are going to produce the same code. I would > stick with between since it is logically clearer. > Yes, this is also what I am seeing here from my timings so far.
> I would also use a single index on either longitude or latitude not > both. This will make the index smaller and denser, and therefore > somewhat faster to access. The second field in a compound index is only > useful if the first field is being tested for equality (i.e where long = > ? and lat between ? and ?). > > I suspect you will get the best results (short of switching to an RTree > index) using a query like this. > Thank you very much, that was very helpful and informative. I will do so. Thnks again, Christophe Leske www.multimedial.de - [EMAIL PROTECTED] http://www.linkedin.com/in/multimedial Lessingstr. 5 - 40227 Duesseldorf - Germany 0211 261 32 12 - 0177 249 70 31 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
