You can configure an include_object() function which can inspect the
model and decide whether or not to include the model in autogenerated
migrations:
http://alembic.readthedocs.org/en/latest/api/runtime.html#alembic.runtime.environment.EnvironmentContext.configure.params.include_object
Then you
I would definitely agree using postgres in both dev and prod is the way
to go here; sqlite behaves sufficiently differently, particularly around
DDL.
At Axial we previously had multiple databases in concurrent use, with
migrations operating on both databases at once. We modified env.py's
run_migra
Hi everyone,
In short, is it possible to use migrations for some declarative
classes, but not others?
A bit more background: Certain parts of our project are relatively
stable, and we want to use a migration tool for those. However, there
are also some components that are highly experimental prot
I suspect that this has been asked before in various ways, and perhaps
there's a way of making the documentation section on "multiple databases"
clearer, but my question is:
Can I use the same migration scripts for multiple database engines, or do I
need entirely separate alembic folders to han
