CONTRACT JOB POSTING:Custom Installer Project for AIR app

Question

We have  a large AIR app which will require a custom installer. If you have experience with Windows MSI installer let me know if you are interested in this contract job and I will provide details.

Answer 1

Joe,
Thanks for your helpful response. I think you're right that the database management steps would happen on app startup after checking a version number stored in the DB.
What I'm wondering, however, is if there's a best practice for managing these incremental changes to the DB. My current direction is to create a class MigrationsManager, that creates an array of class Migration ( with a single migrate() function ) to manage each necessary and incremental change. Meanwhile, a "migrations" table has one column "version" with a UTC timestamp as an integer and is updated on each migration.
Rails does migrations with up() and down() functions on their base migration class, but the down() function isn't applicable since I can't imagine I would be rolling back earlier migrations on a user's DB.
In the end, I guess I'm just fishing of the best way of managing the different scenarios encountered when 3 years down the road you have an audience with all kinds of different versions of your app/db because of differences in how assiduous they were in updating to the most recent version.
- Daniel