Thanks Mario. I did think about stripping the indexes to cut down the size. Recreating them on-device wouldn't be difficult (just time-consuming) but offset against the smaller download it's possibly worth it... although if I'm into partial on-device db creation then I should really do some timing to see whether importing the whole .dump file on the device is really that bad. Anyway, cheers for the advice.
L On 5 March 2012 21:06, Mario Becroft <m...@becroft.co.nz> wrote: > I don't know whether this is practical in your application, but if you > want to reduce redundancy in the database file when downloading, the > obvious thing is to leave off the indexes, and generate them once the > file is downloaded onto the device. This way you'll have to download > only the actual data set, and this combined with compression should be > about as small as you can go without using domain-specific data > compression or reformulating the data model. > > This is similar to loading from DML statements, which you don't want to > do, but executing only the CREATE INDEX statements after downloading > might be more acceptable than loading the entire data set. > > -- > Mario Becroft <m...@becroft.co.nz> > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
