bmontgomery / databaseversioning Goto Github PK

Allow injection of a logging provider which can be utilized to keep track of upgrades.

In order to develop certain upgrade scripts, you have to know the database name. For instance, when you want to script out a Sql Server Job, you need to know the name of the database inside the script.

I think we should make the database upgrader pass a parameter called something like "@DatabaseName" to each script. Then, in the command line tool, allow the developer to specify the name of the database, which will be passed to all the scripts, on the command line.

Even better, allow any number of parameters to be passed in to each script so you can pass all kinds of different configuration parameters to each script.

The patch scripts don't seem to be actually run multiple times, but the record that the patch script was run is put into the table every time you run the tool, even when it doesn't run the script.

I'd like to see what version the database is before and after the upgrade to make sure the app is running against the correct version of the database.

When you run the tool, it should assume the current directory is the root directory, and it should assume the names of the upgrade scripts, patches, stored procedures, etc. directories. This would make it easier to use.

The tool doesn't let you upgrade to a particular version, which might be helpful, and not that hard to develop.