On 4/1/17, J Decker <d3c...@gmail.com> wrote: > On Sat, Apr 1, 2017 at 2:38 AM, Richard Hipp <d...@sqlite.org> wrote: > >> On 4/1/17, J Decker <d3c...@gmail.com> wrote: >> > I get this ... from sqlite error log callback >> > >> > Sqlite3 Err: (283) recovered 6942 frames from WAL file >> > C:\eQube-Tools\flashboard\server\option.db-wal >> > >> > pretty much every time I restart the program now (espcially if it >> > segfaults). >> >> This is because the previous process to access the database did not >> call sqlite3_close() prior to exiting, and so the WAL file was not >> cleaned up properly. >> > > Right; I understand that; but on the next open, couldn't the wal get > cleaned after recovery? or something... >
"Cleanup" and "recovery" are the same thing. That is exactly what it happening, and that is what is generating the warning in the log. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
