Thanks, but how can I inspect the revisions in code? I'd need to provide
some special markers on the ones I don't want to surround in a transaction.
pt., 10 sie 2018 o 20:50 Mike Bayer napisał(a):
> On Fri, Aug 10, 2018 at 2:00 PM, Michał Bultrowicz
> wrote:
> > Hey!
> >
> > What approach
On Fri, Aug 10, 2018 at 2:00 PM, Michał Bultrowicz
wrote:
> Hey!
>
> What approach would you recommend if we want to run some revisions outside
> of a transaction, but then run the other ones normally?
>
> Let me illustrate that. Let's say we have revisions 1,2,3,4,5. The database
> is currently
Hey!
What approach would you recommend if we want to run some revisions outside
of a transaction, but then run the other ones normally?
Let me illustrate that. Let's say we have revisions 1,2,3,4,5. The database
is currently at revision 1, so we need to run 2-5. The problem is that 4 is
an
On Fri, Aug 10, 2018 at 6:47 AM, wrote:
> Hello
>
> I'm trying to use alembic to generate a migration file in a multi-db
> environment. I first created the project using `alembic init --template
> multidb alembic`
> and then hack the `env.py` script (didn't touch to `run_migration_online`)
> to
Hello
I'm trying to use alembic to generate a migration file in a multi-db
environment. I first created the project using *`alembic init --template
multidb alembic`*
and then hack the `env.py` script *(didn't touch to `run_migration_online`)*
to suit my needs.
Here is the error I got after
