what's special about what you're trying to do? how about just, run the migrations on pc1, run them on pc2, pc3, etc. ?
is the special thing: 1. there's a pre-existing schema that is before you have any migrations? run that pre-existing schema on pc1, pc2 , pc3, etc first 2. there's some kind of data being transferred across? 3. ? On 7/8/14, 3:54 PM, Dorian Hoxha wrote: > So I'm using flask-migrate, that is a simple wrapper to alembic. Is > the write way to use alembic on both computers (so migrations work > correctly on both) by doing: > > 1. init on pc1 with a clean db and an existing models.py file > 2. migrate and upgrade on pc1 > 3. export db and import on pc2 > 4. migrate and upgrade on pc2 > > Is this the way or is there another way to make it work ? > > > Thanks > > -- > 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 > <mailto:sqlalchemy-alembic+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
