Re: Getting the current dialect name in a migration

2016-06-03 Thread Michal Petrucha
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

Re: Getting the current dialect name in a migration

2016-06-03 Thread Mike Bayer
op.get_bind().engine.name On 06/03/2016 10:21 AM, Michal Petrucha wrote: 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

Re: Getting the current dialect name in a migration

2016-06-03 Thread Michal Petrucha
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

Re: Getting the current dialect name in a migration

2016-06-03 Thread Mike Bayer
op.get_bind().name should do it On 06/03/2016 03:25 AM, Michal Petrucha wrote: 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

Getting the current dialect name in a migration

2016-06-03 Thread Michal Petrucha
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