On Fri, Jun 03, 2016 at 10:24:23AM -0400, Mike Bayer wrote:
>
>
> op.get_bind().engine.name
/me hangs his head in shame.
Thanks, I probably should have tried that.
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy-alembic" group.
To unsubscribe from
On Fri, Jun 03, 2016 at 10:05:31AM -0400, Mike Bayer wrote:
> op.get_bind().name should do it
Alas, I have already tried that:
if op.get_bind().name == 'postgresql':
AttributeError: 'Connection' object has no attribute 'name'
Michal
--
You received this message because you are subscribed
Hi everyone,
I remember seeing a quick expression that extracts the name of the
dialect in use from alembic.op, but I can't find it anywhere now, and
I can't figure it out by myself either. Does anybody know the right
chain of attributes and/or method calls to follow from alembic.op to
get to
On Fri, Jan 22, 2016 at 09:59:39AM -0500, Mike Bayer wrote:
> I see in
>
> batch_op.alter_column(name, type_=sa.Integer(),
> existing_type=sa.Boolean())
>
> you aren't giving it the constraint name in the existing_type, that's
> actually where the
> "_unnamed_" is coming from.
Yeah, I've
On Wed, Nov 18, 2015 at 08:07:09AM -0500, Jon Rosebaugh wrote:
> Sure, but declarative classes have a table.
>
> MyModel.__table__.info['exclude_from_autogen']=True
>
> (you'll probably want to write a class decorator that sets this,
> actually.)
Oh, of course. Thanks a lot for the help!
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
