Hi all, For testing purposes, I created a single row with a large blob (hundreds of megs) in my database. There is also an integer column. When I do an update on the integer, the query is very slow, and there's a lot of disk activity. The bigger the blob, the slower the query (a rule of thumb - one second per 20 megabytes of blob size on a low-end PC). Synchronous is OFF.
The time of write to an integer should not depend on the other fields' contents. I know that Sqlite, by design, allows variable-length records everywhere, including INTEGER columns. But in this case both the old and the new lengths are identical. So what's the cause of this, and is there a workaround? Thanks, Yaroslav. -- View this message in context: http://www.nabble.com/Large-blobs---slow-UPDATEs-on-non-blob-columns-tp19829079p19829079.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
