Thanks Simon, for the answer. David, sqlite3_rekey_v2() is a function to change the database encryption key - it's a SEE feature.
On Fri, May 3, 2019 at 9:56 AM Jens Alfke <j...@mooseyard.com> wrote: > > > > On May 3, 2019, at 8:37 AM, Simon Slavin <slav...@bigfraud.org> wrote: > > > > While rekey is working, the database temporarily contains both sets of > some data. Automatic crash recovery will see, this, recover the > unconverted set, and wipe the converted set. You do not need to take > special precautions. > > Thanks, Simon. So the rekey is expected to double the database file size? > That’s good to know. > After the call completes, is the file size back to normal, or is a vacuum > needed to reclaim disk space? > > It would be good to update the SEE docs to describe this, as storage space > can be a significant issue on a resource-constrained device. > > —Jens > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
