Upgrade StorageTried installing Better Bibtex and keep getting corrupted sqlite message
Hello
I am trying to integrate Obsidian with Zotero to add citations easier
Better Bibtex failed and generated errors
I tried the database repair tool but that did not solve the issue and I saw that the tool has a warning that it may not solve all issues
Thus I am looking for advice
I went down a rabbit's hole using AI guidance thinking it was an easy fix
I use local only so no cloud sync available
Database stored on local machine only
I'm using Zotero 9 (not sure if that makes a difference)
Thanks in advance for any advice
I am trying to integrate Obsidian with Zotero to add citations easier
Better Bibtex failed and generated errors
I tried the database repair tool but that did not solve the issue and I saw that the tool has a warning that it may not solve all issues
Thus I am looking for advice
I went down a rabbit's hole using AI guidance thinking it was an easy fix
I use local only so no cloud sync available
Database stored on local machine only
I'm using Zotero 9 (not sure if that makes a difference)
Thanks in advance for any advice
This discussion has been closed.
Thanks for the quick reply.
I will try to contact the plugin developer as well.
But this is the reason I thought of the sqlite issue. I got the following error messages (shown in the images) when performing the installation and subsequently trying to repair the sqlite. I hope this describes the situation better.
First I tried the Zotero repair tool from https://www.zotero.org/utils/dbfix/ and replaced the sqlite file
When that didn't work and generated the other error messages I tried the restore from automatic backup option in one of the messages.
The problem only surfaced with BBT enabled. So I thought (well AI stated) that BBT identified a pre-existing issue as it scans the directory ("When Better BibTeX initialised, it tried to scan your library and immediately bumped into this existing Zotero issue. Better BibTeX did not destroy or corrupt your library; it simply exposed a flaw that was already sitting in Zotero's local database file.")
https://s3.amazonaws.com/zotero.org/images/forums/u13962295/7cymnvtid2l47dnym3ud.jpg
https://s3.amazonaws.com/zotero.org/images/forums/u13962295/krtuybav1lj0mpt943br.jpg
https://s3.amazonaws.com/zotero.org/images/forums/u13962295/dpbbe7217xtvcm96njha.jpg