5.0.1-alpha

Changes in this release

• Dropped the useless command/extension/plugin design - Horton should only do one thing, and that is execute migrations.
• Database name is a require command parameter.
• Simplified the migration modification logic. Execution will simply stop which a conflict is detected. Execute with the --rerun parameter to rerun modified migrations.
• Added a --baseline parameter to record scripts without actually running them.
• Cleaned up and streamlined output for automation.

4.3.0

New features in this release:

• Horton learned the ADD-MIGRATION command which will create a blank migration (with a specified name) in the provided migration scripts directory using the next available integer prefix.

4.2.0

New features in this release:

• Horton learned how to accept an ADO.NET connection string with the -c argument. You can use this instead of passing server/database/username/password.
• Horton now exits with an error code of 1 when it aborts early (e.g. migration conflict or an exception).
• Horton prints less to the console when running --UNATTEND to compact the output.
• Horton will print its version number with -v or --version.

4.1.0

Issues resolved in this release:

• "Desired State for Stored Procedures" #3

4.0.0

4.0.0 is a significant rewrite and is entirely incompatible with previous versions!

Notable Changes

• Rewritten command line parser and new command line arguments.
• New conventions around command line arguments. Some are optional, others can be inferred from environment.
• Redesigned schema_info table.
• Cleaner separation between database specific code and the general horton program code. Data access is all based on ADO.NET, so in theory I should be able to support any provider.
• Supports arbitrarily named "repeatable" scripts that can exist in any sub-directory.