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
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
On 11/16/2015 07:38 AM, Donald Stufft wrote:
> I am currently using the SQLAlchemy ORM and I'd like to be able to start
> up transactions using PostgreSQL's SERIALIZABLE READ ONLY DEFERRABLE
> isolation level. I don't want every single transaction to use this
> isolation level nor do I have the
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
On Tuesday, November 17, 2015 at 9:14:51 AM UTC-5, Michael Bayer wrote:
>
>
> conn = session.connection()
> conn.detach()
> conn.execute("set session isolation ")
>
> < work with connection>
I use this strategy, but without `detatch`. I do this with SqlAlchemy in a
webapp context, so I
I can't find anybody who has tried to do this, and I'm not sure that it's
really possible with
sqlalchemy, but I'd like to see if anybody has any ideas.
Basically, I'd like to map to database tables that are not static. I'm
trying to wrap a system
that has a whole bunch of tables that are
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
