Turns out the previous commit did fix a bug that could arise and produce
the same error as described by Issue #22, but in fact Issue #22 is down
to a database compatibility issue with SQLite 3. Hopefully fixed by this
change.