Interviewed by CNN on 11/07/2011 12:06, Gerald Ross told the world: > I noticed a file named places.sqlite.corrupt. Can this be safely > deleted? It is much larger than the places.sqlite file.
Well, from what I understand this is what happens when Seamonkey is unable to understand the places.sqlite file -- it gets renamed to places.sqlite.corrupt and a new one is created from scratch. Meaning you lost all your history, bookmarks and such. One situation (it's not the only one) where this might have happened is if you went back to Seamonkey 2.0 after testing Seamonkey 2.1 or 2.2 in the same profile: the newer version add changes to the places.sqlite database that the old version does not understand, and therefore considers the file "damaged." If you DID go back to SM 2.0 at some point and are wondering what happened to your old bookmarks, you MIGHT attempt to rename the places.sqlite.corrupt back to places.sqlite to check if your old bookmarks are there. But do back up the current places.sqlite file before that. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my wrist radio. *Added by TagZilla 0.066.2 running on Seamonkey 2.1 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
