how to handle migrations in modules

[alfredbez]

It would be nice to be able to execute migrations from modules directories aswell. Most modules use currently the onActivate() but implement their own logic which reads a SQL file in most cases.

We could overwrite

oxid-console/src/Core/Migration/MigrationHandler.php

Line 218 in 83050a0

protected function _buildMigrationQueries()

to load the migrations not only from the migration directory but from all migration directories in the modules directory.

I'm not sure if this is only needed for running migrations or for generating them, too. That would be a bit more hassle since we need to extend the template to include a specific namespace, put the migration file into a different directory + check if the directory exists etc.

[smxsm]

In the first step it would be enough to just load them from the modules directory. You can always generate them and just copy the files to your module dir.