-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There isn't a documentation or wiki page about the blob i/o functionality beyond the api reference. I am curious if the behaviour I am seeing was intentional.
Open a blob for reading. Insert into the same table (not affecting the blob or its row). On calling sqlite3_blob_read, I get SQLITE_ABORT returned and the errmsg is "not an error". This also happens if I do a few reads, and then the insert, on the next read. (This also happens with blobs open for writing and doing read or write after the table is changed). Open a blob for reading. Call sqlite3_blob_write, and get back SQLITE_READONLY. On next calling sqlite3_blob_close, I also get back SQLITE_READONLY. If sqlite_blob_close is going to return any errors from prior reads/writes then it should also do so for the above paragraph (which it doesn't). You can delete (via SQL) a blob that is open. The next sqlite3_blob_read on the blob gets SQLITE_ABORT. (Heck you can even change the contents via SQL). It isn't stated anywhere what the transactional nature of blob i/o is. For example is data committed after each write, or does it happen on the close. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHUluYmOOfHg372QQRAr6wAKCyo4lRyfeu5gtAxJ+yfH8/KFhhGwCfTV36 F5Z1rGEiL8hjdSMIC+XjWTs= =nd4s -----END PGP SIGNATURE----- ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
