Comment 1 for bug 988454

This is because the database schema has been updated recently and an attempt to open a database that was generated with a previous revision of the code has been made.

I'm afraid there's no database migration path for now, so the solution for this is to regenerate the database. Anyway, I'll keep this bug opened and think about adding a clearer error message in the future.