This PR contains several improvements regarding performance, filtering and possible values for the backend UI.
In versions 1.2.0-1.2.3 we had the migrations reverted to standard migrations. In 1.2.4 we added the namespaced migrations back and moved the "classic" migrations to migrations/1.1.x. So this PR should be BC, but it would be nice if someone using namespaced migrations could confirm this.
For future migrations we'd need to create a new folder eg. migrations/1.3.x or migrations/v2, which would also have to be configured. This is a bit ugly, but we found no other way to keep projects which started with non-namespaced migrations updateable. For these new migrations we can use namespaced migrations, but they have to reside in a separate folder or namespace.
Another option would be to provide namespaced and non-namespace migrations for the future, maybe a bit nice with class m1234 extends from namespace\migration\m1234. That would be up to discussion.
In general we'd like to keep the development going here.
This PR contains several improvements regarding performance, filtering and possible values for the backend UI.
In versions 1.2.0-1.2.3 we had the migrations reverted to standard migrations. In 1.2.4 we added the namespaced migrations back and moved the "classic" migrations to
migrations/1.1.x. So this PR should be BC, but it would be nice if someone using namespaced migrations could confirm this.For future migrations we'd need to create a new folder eg.
migrations/1.3.xormigrations/v2, which would also have to be configured. This is a bit ugly, but we found no other way to keep projects which started with non-namespaced migrations updateable. For these new migrations we can use namespaced migrations, but they have to reside in a separate folder or namespace.Another option would be to provide namespaced and non-namespace migrations for the future, maybe a bit nice with
class m1234 extends from namespace\migration\m1234. That would be up to discussion.In general we'd like to keep the development going here.