FlashDB icon indicating copy to clipboard operation
FlashDB copied to clipboard
verified publisher icon armink

Document upgrade and downgrade processes

Open zamazan4ik opened this issue 3 years ago • 3 comments

Hi.

After reading the documentation it is not clear for me, how upgrade and downgrade processes should be performed over the database. Could you please describe somewhere in the documentation:

  • How to upgrade the database to the newer version (hopefully with no downtime)
  • How to downgrade the database to the older version (hopefully with no downtime)
  • Maybe some compatibility policies and notes between versions

Thanks in advance!

zamazan4ik avatar Aug 04 '22 20:08 zamazan4ik

Hi. Which capability is the database upgrade? Can you give an example?

armink avatar Aug 05 '22 01:08 armink

Sure. With a "upgrade" word I mean upgrading FlashDB version to the newer version, e.g. 1.0 -> 1.1. "Downgrade" is the same but in a vice versa direction: 1.1 -> 1.0.

Why this information is important for the users? Because if the upgrade/downgrade processes are complicated (or even not supported without full reexport), it could be much harder for the users perform their usual regular upgrades (and downgrades, if something goes wrong with the newer database version).

zamazan4ik avatar Aug 05 '22 08:08 zamazan4ik

OK, I known. The database format of FlashDB from V1.0 to V1.1 are fully compatible. It's just a functional enhancement. If there is an incompatible version, I will write it in the documentation.

armink avatar Aug 05 '22 09:08 armink