Options
Versioning
Brian Donahue
Posts: 6,590 Bronze 1
Hello,
That's an interesting idea. You would really need to have the versioning information in the database, though.
On our internal software, we have a version table, and distributing an update means that our update package contains a series of scripts -- an upgrade from 1-1.1, 1.1-1.2, etc.
We select from the version table to determine which script to start at and then run all of the following scripts to bring the database up to the current version.
If we were to use Packager to do the upgrade, we'd need to add conditional running of scripts and be able to embed multiple scripts in one package.
Have you got a different idea in mind?
That's an interesting idea. You would really need to have the versioning information in the database, though.
On our internal software, we have a version table, and distributing an update means that our update package contains a series of scripts -- an upgrade from 1-1.1, 1.1-1.2, etc.
We select from the version table to determine which script to start at and then run all of the following scripts to bring the database up to the current version.
If we were to use Packager to do the upgrade, we'd need to add conditional running of scripts and be able to embed multiple scripts in one package.
Have you got a different idea in mind?
This discussion has been closed.
Comments
We shall see. The ability to edit the SQL script before packaging it is a fairly popular suggestion.