Re: [sqlalchemy] Re: long transaction after database switched over

2018-05-16 Thread jiajunsu . zju
This patch worked. https://gerrit.sqlalchemy.org/#/c/zzzeek/sqlalchemy/+/747/ But I didn't get the log "Double checkin attempted", maybe the real working code is if connection_record and connection_record.fairy_ref is not None: connection_record.checkin() 在 2018年5月16日星期三 UTC+8下午4

Re: [sqlalchemy] Re: Composite index using naming convention

2018-05-16 Thread Mike Bayer
On Wed, May 16, 2018 at 6:59 PM, HP3 wrote: > Thank you Mike, > > But I just noticed that the index name is not showing all the columns used > in the composition. > > CREATE INDEX ix_mymodel_prop_a ON mymodel (prop_a, prop_b) > > I was expecting: > > CREATE INDEX ix_mymodel_prop_a_prop_b ON mymode

[sqlalchemy] Re: Composite index using naming convention

2018-05-16 Thread HP3
Thank you Mike, But I just noticed that the index name is not showing all the columns used in the composition. CREATE INDEX ix_mymodel_prop_a ON mymodel (prop_a, prop_b) I was expecting: CREATE INDEX ix_mymodel_prop_a_prop_b ON mymodel (prop_a, prop_b) In my case, it failed because `prop_b

Re: [sqlalchemy] Composite index using naming convention

2018-05-16 Thread Mike Bayer
On Wed, May 16, 2018 at 4:42 PM, HP3 wrote: > Hello: > > How can one create a composite Index whose name follows the naming > convention declared in Meta? > > We are using naming convention for all ORMed classes per > http://docs.sqlalchemy.org/en/latest/core/constraints.html#configuring-constrain

[sqlalchemy] Composite index using naming convention

2018-05-16 Thread HP3
Hello: How can one create a composite Index whose name follows the naming convention declared in Meta? We are using naming convention for all ORMed classes per http://docs.sqlalchemy.org/en/latest/core/constraints.html#configuring-constraint-naming-conventions but explicit Index'es end up wit

Re: [sqlalchemy] Issue with Sqlalchemy in exe file(created using pyinstaller)

2018-05-16 Thread Simon King
On Tue, May 15, 2018 at 8:59 PM, wrote: > I have been struggling for a few days due to an issue with SQLAlchemy. > > The line of code which is giving problem is > > engine = > sqlalchemy.create_engine('teradata://pwd@DBinstance?driver=Teradata') > > This code works perfectly fine while running fr

Re: [sqlalchemy] Re: long transaction after database switched over

2018-05-16 Thread jiajunsu . zju
Thanks a lot. I'll test this patch in our environment. 在 2018年5月16日星期三 UTC+8上午2:58:56,Mike Bayer写道: > > good news, I reproduced it. > > Even better news for you, vindication! nothing to do with greenlets, > threads, concurrency, or anything (though it doesn't have to do with > the "del" or th