> I've run into exactly the same thing on both version 2 and 3, commented > on it here before too. What Someone suggested here and it works, is to > initially open and read the file as if it were a data file. I do it 64K at a time. > Then close it and open with sqlite, in my case that took the 30 second > initial stall and dropped it to about 1-2 seconds. I haven't tried memory > mapping and scanning forward but, that might work too. The DB where > it had the most affect is about 10 megs.
I just tried reading the file in 1-MB chunks and it seems to work very well. Thank you. I started on memory mapping but after a cursory glance through the API's it looked like too big of a deal. ;) Amazing that it can drop the time so enormously. Well, lesson learned till next time. / Mats
