Database bloats, no options to prevent Rated 3 out of 5 stars

lazarus.sqlite is now larger than places.sqlite. I've filled in (paste) some huge "forms" for bug reports, blog posts, and such - often edited revisions and it seems to remember EVERY ONE.

It has saved me several times, but there should be some way of purging huge text areas or large objects and compact the database. I would like to recover large forms from a crash or mistake. But I never need them a few days later.

Right now the only thing I can do is delete the entire database or watch as it grows without limit. And I don't want to limit them by date - some sites I visit infrequently but want to keep the info, and some I visit often but don't need to keep the data.

Some kind of purge, clean, and compact is all that would be needed for me to consider this near perfect. But the keep all or delete all or single expire setting isn't adequate.

This review is for a previous version of the add-on (2.0.4). 


This is (hopefully) resolved in the latest version, which allows you to "vacuum" the database as and when required. Get it from

Also, just a gentle reminder about AMO reviews policy - rather than posting bug reports in a review you should use the support contact associated with the add-on (in this case, lazarusATinterclueDOTcom) to make a bug report rather than posting it in a review. If the add-on developer fails to respond appropriately, eg by fixing the bug in the next release, then talking about it in a review becomes more appropriate. Often there will be things about your system (eg, the operating system and firefox version) that the developer needs to known in order to debug the problem, and an AMO profile usually does not allow the addon author to find out who you are and ask these questions.