On Sat, 12 Oct 2013 21:48:50 -0400 Richard Hipp <d...@sqlite.org> wrote:
> The iPhone is using the default method, which is to leave the bytes > intact and simply mark the deleted region of the page as available > for reuse by a subsequent INSERT. That is the default method because > it is faster. Zeroing out the deleted fields, while quick, does take > measurable time. > > We added the SQLITE_SECURE_DELETE compile-time option and the "PRAGMA > secure_delete=ON" command for Firefox. I've got the secure_delete option turned off, it's not zeroing the whole record/payload, only the first two fields ( payload length, rowid ). Intact record, before removal; 81 16 86 30 05 1D 47 81 65 52 45 4D 4F 56 45 4D ...0..G.eREMOVEM Removed using sqlite3 cli [ Ubuntu 13.04 ], secure_delete = 0; 00 00 00 9A 05 1D 47 81 65 52 45 4D 4F 56 45 4D ......G.eREMOVEM That said, I'm not sure what the significance of the 9A is. The 05 byte is the payload header size varint (5 bytes). Paul. -- Computer Repairs for Charters towers - http://ctpc.biz A.B.N. 19 500 721 806 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users