alembic history -r current:head is perfect.
Thanks!
On Tue, Dec 2, 2014 at 4:28 PM, Michael Bayer
wrote:
>
>
> > On Dec 2, 2014, at 4:06 PM, Daniel Son wrote:
> >
> > Hi,
> >
> > Is there a way to have a dry run for alembic revision?
> > Or a ver
Hi,
Is there a way to have a dry run for alembic revision?
Or a very easy way to detect an error case via the command. For example, I
have 2 revisions that have just branched and now I need to create a merge
point as the next revision.
I'm trying to create a build hook that catches this case an
Hi,
I'm new to SQLalchemy and alembic and I'm doing a proof of concept for
migrations in Redshift.
Initially, using the regular postgresql dialect everything is fine.
But when I try to use the redshift_sqlalchemy dialect for the last bit of
Redshift functionality, it goes caput.
And I've looked
