Re: [sqlalchemy] Re: Differences between `op.get_bind()` and `op.get_bind().engine.connection()`

On Wed, May 15, 2019 at 5:23 AM Diego Quintana wrote: > > Hello again! > > This worked, thanks! > > I noticed that if I use `bind.connection`, I do not need to call > `engine.raw_connection` anymore. I wonder why is this. Is this a proxy to a > raw connection or it was never necessary from the s

[sqlalchemy] Re: Differences between `op.get_bind()` and `op.get_bind().engine.connection()`

Hello again! This worked, thanks! I noticed that if I use `bind.connection`, I do not need to call `engine.raw_connection` anymore. I wonder why is this. Is this a proxy to a raw connection or it was never necessary from the start? Thanks! Am Freitag, 10. Mai 2019 13:09:04 UTC+2 schrieb Diego

Re: [sqlalchemy] Re: Differences between `op.get_bind()` and `op.get_bind().engine.connection()`

On Fri, May 10, 2019 at 10:34 AM Diego Quintana wrote: > > Thanks for your answer. If I got this right, it makes sense to think of two > different transactions happening, being the second one not able to "see" what > the first has done (e.g. creating tables) until it has finished (i.e. when > t

[sqlalchemy] Re: Differences between `op.get_bind()` and `op.get_bind().engine.connection()`

Thanks for your answer. If I got this right, it makes sense to think of two different transactions happening, being the second one not able to "see" what the first has done (e.g. creating tables) until it has finished (i.e. when the migration has already ended). Sort of a race condition, if it's