Correct, that is what I did. Except, I do a conn.close() at the end rather than a del.
On Tue, May 13, 2014 at 4:10 PM, Michael Bayer <[email protected]>wrote: > > On May 13, 2014, at 2:23 PM, Sylvester Steele <[email protected]> > wrote: > > > ODBC connection pooling setting did not matter. After the above change, > code is running in both cases (ODBC connection pooling on or pooling off). > > Let me know if this is an issue and you need more info. > > > OK so I’m guessing you did something like this: > > conn = engine.connect() > raw_connection = conn.connection.connection > > del conn # conn goes out of scope > > > > so yeah, that will break like that. What you can do is stick with > “conn.connection” at least, that’s the so-called “Connection Fairy” which > will keep the DBAPI connection checked out until it goes out of scope. > > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "sqlalchemy" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/sqlalchemy/hRyAeD0xWv0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
