that's not true. As I wrote, I cannot change structure of database, but i did my own test and indexes as are
PRIMARY KEY (x, y, z, s) are almost twice faster for query on single row by x, y, z values (for reading and mainly for writing), then classic ID INTEGER PRIMARY KEY I'm not database expert, but this are measured values! and finally, for me, in this case, speed is not primary! Problem is that I cannot use database bigger then 2GB. But, problem is solved as I wrote in my previous post. Thanks all very much for you time and if anyone of you is Locus user - Sorry, but more then 2GB bigger maps, aren't allowed now :) On Jan 15, 8:55 am, Frank Weiss <[email protected]> wrote: > As I recall, there were no indexes on the table. Without indexes I would > expect most every query on a very table to be very slow. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
