v2.0.203

Changes:

• #97: #96 publish arm64 packages
• #96: publish arm64 packages
• #95: 93 [linux] dingo can only be run as root
• #93: [linux] dingo can only be run as root

This list of changes was auto generated.

v2.0.179

Release notes

Changes:

• #91: feat: #90 add patch type identifier to DB and skip system patches on revert
• #90: reverting when only system patch applied spams warnings

This list of changes was auto generated.

v2.0.167

Release notes

Changes:

• #89: 82 set migration paths on configuration file
• #82: set migration paths on configuration file
• #85: revert migrations in reverse order
• #88: fix: #85 revert migrations in reverse order
• #87: chore: seal classes and mark as internal + cleanup
• #64: add option to apply / revert migrations in transaction
• #86: #64 add option to apply / revert migrations in transaction
• #84: Bump actions/download-artifact from 1 to 4.1.7 in /.github/workflows

This list of changes was auto generated.

v2.0.150

Release notes

Summary

• long needed application refactoring in order to support easier extensibility and testability
• applying migrations in both directions: up and down
• support multiple configuration profiles
• performance improvements
• support more flexible configuration using:
  • configuration file (json, yaml)
  • environment variables
• configurations are stored in .dingo directory instead of single file
• rapid DB development tools. DB functions to check table, column and index existence; easy removal of DB objects and much more
• switched from linq2db to dapper
• dingo DB objects are stored in dingo schema instead of public / dbo
• specify paths that need to be re-applied in every patch
• improved migration validation
• improved unit and integration tests
• supported platforms: linux, macOS and windows
• supported DBMSs: PostgreSQL, SqlServer
• upgrade dependencies
• brand new wiki section

Changes:

• #83: #80, #81 fix issues with down command
• #80: force flags are required
• #81: dingo down default count is 0

This list of changes was auto generated.

v2.0.148

Release notes

Summary

• long needed application refactoring in order to support easier extensibility and testability
• applying migrations in both directions: up and down
• support multiple configuration profiles
• performance improvements
• support more flexible configuration using:
  • configuration file (json, yaml)
  • environment variables
• configurations are stored in .dingo directory instead of single file
• rapid DB development tools. DB functions to check table, column and index existence; easy removal of DB objects and much more
• switched from linq2db to dapper
• dingo DB objects are stored in dingo schema instead of public / dbo
• specify paths that need to be re-applied in every patch
• improved migration validation
• improved unit and integration tests
• supported platforms: linux, macOS and windows
• supported DBMSs: PostgreSQL, SqlServer
• upgrade dependencies
• brand new wiki section

Changes:

• #79: Bump Npgsql from 7.0.6 to 8.0.3 in /Src/Dingo.Core
• #78: Bump Microsoft.Data.SqlClient from 5.1.2 to 5.1.3 in /Src/Dingo.Core

This list of changes was auto generated.

v2.0.143

Release notes

Summary

• long needed application refactoring in order to support easier extensibility and testability
• applying migrations in both directions: up and down
• support multiple configuration profiles
• performance improvements
• support more flexible configuration using:
  • configuration file (json, yaml)
  • environment variables
• configurations are stored in .dingo directory instead of single file
• rapid DB development tools. DB functions to check table, column and index existence; easy removal of DB objects and much more
• switched from linq2db to dapper
• dingo DB objects are stored in dingo schema instead of public / dbo
• specify paths that need to be re-applied in every patch
• improved migration validation
• improved unit and integration tests
• supported platforms: linux, macOS and windows
• supported DBMSs: PostgreSQL, SqlServer
• upgrade dependencies
• brand new wiki section

Changes:

• #75: docs: update install on macOS section
• #74: docs: update install on macOS section
• #73: dingo v2
• #67: set docs pages deployment protection rule
• #45: need to reapply functions / procedures when edited user defined type
• #72: feat: #45 need to reapply functions / procedures when edited user defined type
• #66: Access to the path '/usr/local/Cellar/dingo/logs' is denied.
• #71: fix: #66 Access to the path '/usr/local/Cellar/dingo/logs' is denied.
• #62: SqlServer command provider
• #70: feat: #62 SqlServer command provider

See More

• #61: update docs
• #68: #61 update docs
• #57: configure CI pipelines to publish packages
• #59: #57 update build pipelines
• #48: code refactoring
• #58: #48 dingo 2.0 + new features
• #55: as a user I want to keep all dingo DB objects in a separate schema
• #46: store all dingo related files in .dingo dir instead of project root
• #47: as a user I want to have config profiles
• #51: Azure pipelines build fails on release/v2.0 branch
• #53: #51 fixed build pipeline
• #50: dingo new command requires migration name contain .sql suffix and then adds .sql to the filename resultin in .sql.sql
• #42: As user I want to have toolset for rapid db development

This list of changes was auto generated.

v2.0.137-rc

Release notes

Summary

• long needed application refactoring in order to support easier extensibility and testability
• applying migrations in both directions: up and down
• support multiple configuration profiles
• performance improvements
• support more flexible configuration using:
  • configuration file (json, yaml)
  • environment variables
• configurations are stored in .dingo directory instead of single file
• rapid DB development tools. DB functions to check table, column and index existence; easy removal of DB objects and much more
• switched from linq2db to dapper
• dingo DB objects are stored in dingo schema instead of public / dbo
• specify paths that need to be re-applied in every patch
• improved migration validation
• improved unit and integration tests
• supported platforms: linux, macOS and windows
• supported DBMSs: PostgreSQL, SqlServer
• upgrade dependencies
• brand new wiki section

Changes:

• #67: set docs pages deployment protection rule
• #45: need to reapply functions / procedures when edited user defined type
• #72: feat: #45 need to reapply functions / procedures when edited user defined type
• #66: Access to the path '/usr/local/Cellar/dingo/logs' is denied.
• #71: fix: #66 Access to the path '/usr/local/Cellar/dingo/logs' is denied.
• #62: SqlServer command provider
• #70: feat: #62 SqlServer command provider
• #61: update docs
• #68: #61 update docs
• #57: configure CI pipelines to publish packages

See More

• #59: #57 update build pipelines
• #48: code refactoring
• #58: #48 dingo 2.0 + new features
• #55: as a user I want to keep all dingo DB objects in a separate schema
• #46: store all dingo related files in .dingo dir instead of project root
• #47: as a user I want to have config profiles
• #51: Azure pipelines build fails on release/v2.0 branch
• #53: #51 fixed build pipeline
• #50: dingo new command requires migration name contain .sql suffix and then adds .sql to the filename resultin in .sql.sql
• #42: As user I want to have toolset for rapid db development

This list of changes was auto generated.

v1.1.69

Release notes

Summary

• fixed an issue when dingo would fail to apply migration on the first run

Changes:

• #44: wrong migration is applied when some migrations are up to date and some are new

This list of changes was auto generated.

v1.1.67

Release notes

Summary

• added text highlighting with colors to make output more readable
• migration name validation
• some bug fixes

Changes:

• #43: Add colors to console
• #32: add migration name validation on apply and create commands
• #40: Some parameters names are mismatch in controllers and operations

This list of changes was auto generated.

v1.0.61

Release notes

Summary

• fixed an issue when dingo would fail to apply migration on the first run

Changes:

• #38: first run on a fresh db fails

This list of changes was auto generated.