On Mon, 10 Jan 2011 20:14:00 -0500, Paul B. Gallagher wrote: > Mark Hansen wrote: > >> The way bookmarks are stored changed between pre-2.1 and 2.1. >> In 2.1, bookmarks are stored in a database rather than in an html file. >> The property mentioned above causes SM 2.1 to export the bookmarks (now >> in a database) to an external html file upon exiting SM. >> >> You still "bookmark this page" just as you always have. > > Does this mean that in case of a crash or hang, SM fails to export the > DB and ... what? The info is lost, or just not backed up?
sqlite is ACID a relational database so commits are atomic. In addition the latest nightly builds come with a version of sqlite that has what they call WAL I think that's their name for redo logs. So even if SM crashes, when it starts up again the sqlite code will replay all uncommitted transactions and update the database to a consistent state. (Disclaimer: I spent ten years managing, coding, and customizing enterprise class Oracle Financials databases but I don't know how much of this applies to toy databases like SQLite). > I know how to go into a broken HTML file and fix it, but what if the > database gets corrupted somehow -- will SM automatically save an empty > HTML file on exit? I'm sure I couldn't go in and fix the DB with SM > still running... > > I'm sure you guys have thought this through, but I haven't. Oh yes the Mozilla Storage team has thought long and hard on these and other much more esoteric issues. For example to improve performance, database writes occur asynchronously on multiple background threads. Phil -- Philip Chee <[email protected]>, <[email protected]> http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
