Re: Alembic: Varying database names per environment?

2019-08-19 Thread Mike Bayer
On Mon, Aug 19, 2019, at 7:24 AM, Scott wrote: > On Monday, August 19, 2019 at 9:58:19 AM UTC+10, Mike Bayer wrote: >> >> >> On Sun, Aug 18, 2019, at 6:50 PM, Scott wrote: >>> Looking to use Alembic to manage migrations. >>> >>> We currently have different database names in each environment,

Re: Alembic: Varying database names per environment?

2019-08-19 Thread Scott
On Monday, August 19, 2019 at 9:58:19 AM UTC+10, Mike Bayer wrote: > > > > On Sun, Aug 18, 2019, at 6:50 PM, Scott wrote: > > Looking to use Alembic to manage migrations. > > We currently have different database names in each environment, so for > dev, test and prod we have db_dev, db_test and

Re: Alembic: Varying database names per environment?

2019-08-18 Thread Mike Bayer
On Sun, Aug 18, 2019, at 6:50 PM, Scott wrote: > Looking to use Alembic to manage migrations. > > We currently have different database names in each environment, so for dev, > test and prod we have db_dev, db_test and db_prod respectively. > > Is this database naming scheme going to be

Alembic: Varying database names per environment?

2019-08-18 Thread Scott
Looking to use Alembic to manage migrations. We currently have different database names in each environment, so for dev, test and prod we have db_dev, db_test and db_prod respectively. Is this database naming scheme going to be compatible with Alembic or am I better off looking to drop the