Skip to content

Releases: bizley/yii2-migration

4.1.1

24 Jul 09:21
370afe6
Compare
Choose a tag to compare

Fixed bug with updater forcing update decimal column with 0 scale.

4.1.0

13 Jul 12:11
2362592
Compare
Choose a tag to compare
  • Added comparing foreign keys triggers ON UPDATE, ON DELETE.
  • Added experimental mode (-ex=1) that allows to use raw SQL column definitions for updater.

4.0.5

21 Jun 11:55
aae331d
Compare
Choose a tag to compare

Fixed bug with invalid column length set up based on old migration.

4.0.4

20 Jun 12:56
90bf1da
Compare
Choose a tag to compare
  • Fixed bug with adding automatically index for foreign key for MySQL subjects even when explicit index has been added before.
  • Fixed bug with referred table name in foreign key not being processed as raw name.
  • Fixed bug with missing first order number in update migration files batch.

4.0.3

18 Jun 16:29
d05efa4
Compare
Choose a tag to compare

Fixed Inspector not resetting applied changes between runs.

4.0.2

18 Jun 11:05
972acab
Compare
Choose a tag to compare
  • Fixed problem with comparing columns' length.
  • Fixed invalid default null column value comparison for SQLite.
  • Column's property isNull is now false by default and cannot be null.
  • Fixed incorrect data scheme for alterColumn method in dummy Migration class.

4.0.1

13 May 18:32
86310b4
Compare
Choose a tag to compare

Fixed bug with column renderer not resetting its flags between renders.

4.0.0

01 May 16:10
Compare
Choose a tag to compare

See Migrating to version 4.0 for migrating guide.

4.0.0-RC2

24 Apr 09:55
38fb8c6
Compare
Choose a tag to compare
4.0.0-RC2 Pre-release
Pre-release

Added support for PostgreSQL schemas thanks to @krepver 💥

3.6.5

19 Apr 06:59
7e9c7df
Compare
Choose a tag to compare
  • TableColumn::removePKAppend() is returning original append value when its column is not a part of primary key and in other case the value of append is not uppercased anymore.
  • New protected property workingNamespace introduced to store the value of current namespace to be applied for fixing migration history.
  • Dummy migration instance is configured now with cloned DB component.