Robert Korulczyk
Robert Korulczyk
In that case using namespaced migrations does not make any sense in most cases - you just can't do anything with it. Non-namespaced migrations can be moved to different directory,...
This is side effect of project refactoring. I keep migrations in modules, and sometimes I need to remove or rename module, so I need also move migrations. I can do...
@klimov-paul You can't move single migration in this way. It is also more like a hack - your migrations namespace is out of sync with directory structure.
Example of changing namespace in migrations: https://github.com/yiisoft/yii2-queue/commit/9edb0a052b5a21056cf624f19815b05dc431b2a5#diff-035fdbf9bbbbf357e2eeeeee4f737f4f
I don't want to modify my migrations history, I want to modify code of my application (including migrations). I already proposed solution for this with keeping history intact (none of...
> That is the same thing: any modfications of the migrations source is a BC break over any other project working copy. No, it's not. It is BC break only...
It works in the same way as installing app from scratch - if you have 1k migrations, first installation will load them all and run. But it will not load...
> In that case how history reverting (migrate/down) should work if same migration is mentioned several times there? It is explained in first post - did you read it? >...
1. Your implementation does not support reverting. 2. It need to be manually configured by the end user - it is useless for extensions/modules authors. 3. It actually modifies migration...