Mattes Migrate Versions Save

Database migrations. CLI and Golang library.

v1.3.2

6 years ago
  • fixes import paths to work with gopkg.in

v3.0.1

6 years ago
  • @fln fixed MySQL multi statement bug
  • @watersofoblivion added AWS Redshift database driver
  • @Menta2L added QL database driver (but see https://github.com/mattes/migrate/issues/232)
  • @fsouza added source drivers for Google Cloud Storage and AWS S3

v3.0.0

7 years ago

Version 3 is a complete rewrite and not compatible with previous versions.

Not all drivers from previous versions are available yet. Any help porting existing drivers to this latest version is greatly appreciated. If you want to continue v1 for now, please have a look at branch v1.

  • Sources are drivers now. That makes it very easy to read migrations from a lot of places, like filesystem, S3, go-bindata, ...
  • Database drivers only have the bare minimum logic to apply migrations. All logic is handled by the core migrate library. This makes implementing and testing drivers even easier.
  • V3 is a complete rewrite. It uses io.Readers internally, is tested for thread-safety (also no leaking goroutines).
  • dirty state was introduced to give database drivers more flexibility to handle failed migrations.

v1.3.1

7 years ago

.

v3.0.0-rc2

7 years ago
  • updated postgres driver
  • added mysql driver

v3.0.0-rc1

7 years ago
  • Push deb file to packagecloud.io
  • Github fixes

v3.0.0-rc0

7 years ago

Package migrate now has all the functionality to run migrations (including dirty state) and thus can be considered feature complete.

What's missing?

  • Better test coverage (package migrate has a pretty decent test coverage already)
  • Postgres will be included in v3.0.0 release for sure. Cassandra and MySQL/MariaDB should make it into v3.0.0 as well. All other database drivers will follow in later releases.

v3.0.0-prev2

7 years ago

.

v3.0.0-prev1

7 years ago

.

v3.0.0-prev0

7 years ago

This is a working preview of the upcoming v3.0.0.

Don't use in production, yet.

Follow development in branch v3.0-prev.