Migrating From 1.5: A Guick Guide

With the release of version 1.6, Sononym has switched to a new database engine. But, if you were running the previous version, there is suddently this big hurdle that must be overcome: to upgrade all the old libraries to the new format.

Shortly after the release, it was clear that the road we offered was more bumpy than anticipated: after installing and launching Sononym 1.6 for the first time, you might see a message saying “Fetching…” for hours on end. And perhaps worse, even if you got those databases up and running, the upgrade process could take a long time. Not good if you depend on Sononym for your daily work.

Once we understood these pain points, we tried to figure out the best path forward, and this is the solution we have arrived at:

• Starting from Sononym 1.6.2, legacy databases will appear much faster in the list of libraries
• Sononym 1.5 and Sononym 1.6.2 will be able to run simultaneously (it used to be strictly a single-instance app)
• The upgrade process in 1.6.2 will be able to complete while not actually replacing the old database.

This allows Sononym 1.6.2 to build/upgrade your databases while you continue to use 1.5. And then, once all databases have been upgraded, you can make the switch by “activating” the upgraded databases.

Put together, it’s our hope that 1.6.2 allows a smooth transition to the newer format.

Share this