>
> Since my code works in blocks, read/compress/encrypt/write, loop. Almost
> all the real data was being written to the compressed file, however any
> finalization and flushing of the stream wasn't occurring (since the encrypt
> was failing) so the last bit of any SQLite database wouldn't be written.
>
> I'm guessing that also contributes to how infrequent I saw a problem.
>
What size blocks where you using?
So, what _is_ stored in the final "block size" length of the DB file? It must
be something not-so-critical as you are able to dump the DB, right?
Perhaps adding a full-file verify pass to your compress/encrypt code would be a
good idea.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
