Pete Zaitcev (zaitcev) wrote,

Attack of Sqlite

Recently it became fashionable to link Sqlite everywhere (for example, yum uses it). The awsum workout that Firefox gives to your kjournald is also Sqlite. But now I see a little problem. What if anything happens to the database?

XML was bad enough, but it is repairable, if with a bigger difficulty than plain text. When GNOME eliminated battstat-applet, and started to throw an funny dialog, I was able to fix it by removing a few files and directories in my ~/.gconf (Thank you, Federico).

Now my Liferea develped a problem. One of the feeds has a phantom item in it: it shows one unread even if there aren't any unread items. If I click "Mark All Read", Liferea crashes. How am I supposed to repair this? I suppose there may be some command line tools coming with Sqlite which allow to issue SQL statements, but without knowing how the database is laid out, I cannot formulate such statements.

I expect this kind of thing to become more common as more people jump on the bandwagon.

Tags: linux, sqlite
  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 4 comments