Upgrade StorageStandalone catch-22
While building a standalone client from a source checkout, I came across a little glitch.
When I set the standalone client to use an existing Zotero database using Gear icon → Preferences → Advanced → Custom, the new path was accepted, but there was a schema version mismatch between the standalone client and the target database. The result was that the client refused to start, and (unless I missed something) there was no obvious way to change the setting back to a directory that would work. In my case, I just fixed the source I was hacking on and rebuilt the client; but someone relying on a prebuilt client could get stuck at that point. It might be better for the client to refuse to accept the setting and issue an error message in the event of a version mismatch.
When I set the standalone client to use an existing Zotero database using Gear icon → Preferences → Advanced → Custom, the new path was accepted, but there was a schema version mismatch between the standalone client and the target database. The result was that the client refused to start, and (unless I missed something) there was no obvious way to change the setting back to a directory that would work. In my case, I just fixed the source I was hacking on and rebuilt the client; but someone relying on a prebuilt client could get stuck at that point. It might be better for the client to refuse to accept the setting and issue an error message in the event of a version mismatch.
-
SimonTicket created.
This is an old discussion that has not been active in a long time. Instead of commenting here, you should start a new discussion. If you think the content of this discussion is still relevant, you can link to it from your new discussion.