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 compatible with Alembic or am I > better off looking to drop the environment suffix?
these are three different URLs and if the concern is putting them into one alembic.ini file, easy enough using separate sections: https://alembic.sqlalchemy.org/en/latest/cookbook.html#run-multiple-alembic-environments-from-one-ini-file though usually staging and production DBs have a password you're looking to keep private, and you'd have a separate alembic.ini on your staging and prod servers. but either way it's all doable > > Thanks, Scott > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy-alembic" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sqlalchemy-alembic+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sqlalchemy-alembic/e61e70a9-c2dc-4880-a839-f36272cbfad7%40googlegroups.com > > <https://groups.google.com/d/msgid/sqlalchemy-alembic/e61e70a9-c2dc-4880-a839-f36272cbfad7%40googlegroups.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "sqlalchemy-alembic" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy-alembic+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy-alembic/c05347e5-80eb-49e7-b3c6-d6f7d29f4fe5%40www.fastmail.com.
