Set migration-dir or scope / internals.migrationMode from config with -e option?
#515 aberto em 3 de nov. de 2017
Métricas do repositório
- Stars
- (2.296 stars)
- Métricas de merge de PR
- (Nenhuma PRs mesclada em 30d)
Description
Hi just trying to figure out how to use db-migrate in a simple way. I have a database.json in a config directory, postgresql so a connection string for a user that has ownership of a database schema I want to work with.
Is there a way to do something like this?
database.json
{
"myConnection":
{
"connectionString": "etc...",
"migrationMode": "myMode",
"migrations-dir": "./migrations/myConnection"
}
}
So that when I do
db-migrate create something
It would create in
./migrations/myConnection/myMode/date-something.js
Or even just a migration directory setting per connection config would be nice.
./migrations/myConnection/date-something.js
I feel writing so much is not ideal would be nice to just write simple command to up or create new migration.
db-migrate create something --config=./config/database.json -v -e myConnection
Easier like this?
db-migrate create something -e myConnection
db-migrate up -e myConnection
Having it in database connection configs would allow to have multiple connections use the same migration scripts but have different databases/schemas.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.