Running migrations on databases with a different names about ruckusing-migrations HOT 4 CLOSED

the environment name is there to specify prod or dev so that you don't have to specify it in your database name too. That's not DRY. Why can't you have the same production database name as your local database ? The migration directory is structured according to the database name in order not to have different database migrations files being put together.
Thanks

from ruckusing-migrations.

We may not control the names of the databases which we are migrating. db_prod and db_dev were examples. They may be called database1 and database2, with names not relating to prod, dev.

I believe it would be more elegant (and useful) to separate the the schema name - ie the application or whatever, from the physical database name so that we are not forced to have databases all with the same name.

from ruckusing-migrations.

In more old versions ruckus have the only file folder, but many environments. You can migrate with one set of migrations on any db from environments. Have the same issue on my project, but solved it in more obvious way:
have the same migrations in both folders. This way allow you to skip some db_env_oriented migrations. For example, you create table for production, but this table already exists in development db. There is no need to run this migration for dev, but prod.

from ruckusing-migrations.

Hi,
Please I've already merged #83 which fixes this problem by specifying a custom folder name in the config like 'directory' => 'custom_name'
Thanks

from ruckusing-migrations.