0.23.1

Fixed

• Fixed: Rivet generates invalid SQL when merging a migration that contains an update to a column and adding a default
  constraint to that same column.

0.23.0

Changed

• Export-Migration no longer includes owner information when it exports Add-Schema operations (i.e. the Owner
  parameter is omitted). When exporting a schema to DDL in SQL Server Management Studio, the owner information is also
  omitted so we think this change should be OK.
• Pushing to a database will now apply the baseline schema if it hasn't been applied.

Fixed

• Baseline schema in schema.ps1 doesn't get applied when pushing migrations.
• The DropDatabase command fails if the database name has non alphanumeric characters in its name.

Removed

Removed the InitializeSchema switch from rivet.ps1 and Invoke-Rivet as it was not actually implemented.

0.22.0

Added

• Verbose messages when connecting to SQL Server and switching databases that shows the current SQL Server and database
  name.

Changed

• Verbose messages that show queries now show query duration in seconds.
• Improvements to Rivet internals.

Fixed

• Get-Migration fails when plugins use Rivet's database connection.
• Rivet fails if a plugin returns non-operation objects to the pipeline.

Removed

• Function Connect-RivetSession. Improved internal Rivet connection management so this function is no longer
  necessary.

0.21.1

Fixed

• Fixed: Connect-RivetSession no longer returns errant boolean values.

0.21.0

Changed

• Added an optional Database parameter to Connect-RivetSession function that allows specifying the default database to connect to when the Rivet session contains multiple databases.

0.20.0

Added

• New-RivetSession function for creating a Rivet session. A Rivet_Session is the object used by Rivet to keep track
  of current state.
• Connect-RivetSession function for connecting to the databases in a Rivet session.

Changed

• Rivet internals no longer use global variables for managing connections and current state.
• Default migration output now quotes SQL Server names and database names with [].
• Verbose output now shows query parameter names and values.

Fixed

• Shows too many errors.
• Remove-ForeignKey prompts for TableName and ReferencesTableName arguments.
• Creating a new migration also creates an unused schema.ps1 file and writes a warning that it should be added to source
  control

0.19.0

• Checkpoint-Migration will no longer delete migration scripts that have been pushed to the database. Instead it will now export rows from the rivet.Migrations table and include them in the schema.ps1 file.
• Added an InitializeSchema switch to the Invoke-Rivet script that is used to initialize database(s) with the schema.ps1 file that is generated from Checkpoint-Migration.

0.18.0

• Fixed: Rivet doesn't use the CommandTimeout property in rivet.json configuration file.
• Export-Migration will now allow references to objects in databases that have been applied before it.
• The DatabaseOrder setting in the rivet.json file has been removed in favor of a new Databases property that should
  be the ordered-list of databases to migrate.
• Export-Migration will now include extended properties on schemas, views, and view columns.

0.18.0-rc1

Export-Migration now includes extended properties on schemas, views, and view columns.

0.17.0

When initializing a database, Rivet now runs the migrations found in the schema.ps1 file, which contains the baseline
database schema upon which all migrations should be applied. You can use the Checkpoint-Migration function to create
a baseline schema.ps1 file for your database(s).