The version numbering that I plan to use for this project is designed to make your life (hopefully) just a little bit easier. Minor releases (the part after the ”.”) indicate that no database upgrade is necessary when upgrading from another release with the same major release (the part before the ”.”) number. Unless you have made your own code modifications, a minor upgrade should consist of simply replacing the contents of the installation directory with the files from the new release.
When a change to the database schema does occur, I will increment the major release number. I will provide scripts that will alter the database schema and move data around as necessary. There will be one such script for each major version change. Thus, If you upgrade from version 2 to version 3, you would only run the v2-v3 upgrade script; but if you are upgrading from version 1 to version 3, you would first run the v1-v2 upgrade script, and then run the v2-v3 upgrade script. (I’m going to try to automate that with a wrapper script that simply asks what version you are upgrading from, though.) Obviously, you will want to back up your database before running these utilities.
(Note: neither version 2 or version 3 have been released as of this writing. They have been mentioned here for illustrative purposes.)
Previous Topic
