Releases: bizley/yii2-migration
2.3.1
3.0.0
2.3.0
Package has been rewritten for more object-oriented approach.
- Minimum Yii version is raised up to
2.0.11
. - Maximum Yii version is set to lower than
2.1.0
. Extractor
class is gone.- Multiple table structure classes have been added.
- General PHPUnit test and MySQL specific tests have been added.
- Default value of
generalSchema
property is now1
.
New features:
TINYINT
andJSON
support added (works only for Yii 2.0.14 and newer).- Non-unique indexes tracking added (works only for Yii 2.0.13 and newer).
ON DELETE
andON UPDATE
options tracking for foreign keys added (works only for Yii 2.0.13 and newer).- Migration history table is automatically skipped when running
create-all
andupdate-all
actions.
2.2.3
2.2.2
2.2.1
2.2.0
Fixes:
- generated namespaced class names are compatible with Yii 2 core,
- because of that decision mechanism has been removed (unnecessary now),
- namespaced migrations can be properly extracted now,
- namespaced migrations are added to history with namespace,
- mixed classic and namespaced migrations can be properly located.
Unfortunately namespaced migrations generated with previous version of this extension must be regenerated or modified manually.
Removed options:
- defaultDecision,
- migrationNamespaces,
Removed option aliases:
- k
2.1.2
Fixes:
- arguments order in Extractor corrected,
- protected methods in Extractor are properly called now,
- unnecessary options for list action in controller removed,
- redundant method renderPrimaryKey() in Generator removed,
- corrected composite primary keys handling,
- primary key constraint name changed to 'primary_key' because of the MySQL error.
Added information in README about renaming columns and tables.
2.1.1
New option added: skipMigrations
List of migrations from the history table that should be skipped during the update process. (default [])
Here you can place migrations containing actions that can not be covered by extractor i.e. when there is migration setting the RBAC hierarchy with authManager component. Such actions should be kept in separated migration and placed on this list to prevent them from being run during the extraction process.
Fixed bugs:
- options available for
update
action are also available forupdate-all
action now.