On Mon, Sep 5, 2011 at 5:02 PM, Pero Mirko <peromi...@gmail.com> wrote:
> - BLOB data should be avoided along with the rest of smaller row data as it > seems to slow things down considerably, the smaller the row and the simpler > data structure - the better. > To elaborate on this a tiny bit: if you have, e.g., a table called "downloads" and it contains the fields (name, downloadCount, theBlob), and you update the download count each time it is downloaded, someone on this list once recommended to me that the blob be stored in a separate table because updating the field requires copying the whole row (and thus the overhead of the blob is disproportionately high, since we are copying it but not modifying it). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
