On 7/13/15 12:46 AM, Mikko Ohtamaa wrote:
Hi,
I am trying to use Alembic in a way that the codebase is split to
several Python packages and each package tracks their own tables and
migration history independently. Effective each package has its own
versions and env.py. Is this possible? I
Hi,
I am trying to use Alembic in a way that the codebase is split to several
Python packages and each package tracks their own tables and migration
history independently. Effective each package has its own versions and
env.py. Is this possible? I assume it is possible as Alembic is pretty
