Regarding: -- 21290 -- full globe view ... is way to slow, it blocks the app 21 seconds - granted, it is the inital start up, but still.
Well, some people aren't satisfied unless they can have the whole world, apparently. ;-) 1) Have you already exhausted tuning the database with larger page sizes, cache sizes, etc. using the PRAGMA commands? (Note that you must recreate your database in order to try a different page size.) Maybe you have and I just missed it in all the emails on this topic. 2) How would selecting the full globe be useful? Would that not return a gigabyte of data consisting of a million table rows? Can your application really make use of these million items or do you instead want this set severely reduced? If it DOES truly want the million rows, then the 21 seconds of database time sounds pretty impressive -- and might turn out to be small compared to the time for you to further process them. If you want it severely restricted, say based on "largest populations" then you may decide to have two city tables -- one for the largest 10000 cities, say, and the other table holding the remaining million. This email and any attachments have been scanned for known viruses using multiple scanners. We believe that this email and any attachments are virus free, however the recipient must take full responsibility for virus checking. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
