On 12/28/2014 6:48 PM, Paul B. Gallagher wrote: > NoOp wrote: > >> SQLite currently uses nine distinct types of temporary files: >> >> Rollback journals >> Master journals >> Write-ahead Log (WAL) files >> Shared-memory files >> Statement journals >> TEMP databases >> Materializations of views and subqueries >> Transient indices >> Transient databases used by VACUUM >> >> Additional information about each of these temporary file types is in >> the sequel. > > Wouldn't it be reasonable to expect SM to clean up these and all other > temp files in the course of a normal shutdown (not a crash or > force-close from the OS)? Or is that level of hygiene too much to expect? > > In that case, shutting down SM on the two machines should purge all temp > files on both, and then copying places.sqlite from one to the other > should create no problems. > > The only way a straightforward copy should cause problems would be if SM > did not complete its housekeeping, right? And if so, deleting > places.sqlite AND the temp files on the target machine should avoid any > repercussions, right? It could even be a cure-all if the target machine > were having trouble and the source machine were not. > > Or am I being hopelessly naïve? > >
Windows 7 Ultimate SeaMonkey 2.26.1 The "temporary" sqlite files are indeed deleted when I terminate SeaMonkey. -- David E. Ross I am sticking with SeaMonkey 2.26.1 until saved passwords can be used when autocomplete=off. See <https://bugzilla.mozilla.org/show_bug.cgi?id=1064639>. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
