On 23 Gen, 19:21, Rick Morrison <[email protected]> wrote:
> Good question, I don't know the answer.
>
> But even if it were a DSN option, it's likely to be an optional one. In the
> absence of an explicit setting, shouldn't we default to having the setting
> off, not on? It sounds as if the pyodbc default is 'on'.
Well... to me it seems the default is "on".. mkleehammer, the pyodbc
maintainer told me that, anyway, even if it's on it should close the
connection anyway when you do the "con.close()" and then "del
con" ( to me this behavior seems the most correct.. it's not nice to
have dead connection opened until the process is dead ). You can read
his answer here:
http://groups.google.com/group/pyodbc/browse_thread/thread/320eab14f6f8830f
>
> I would argue for forcing it off anyway, even if set on: this potential
> double-layered pooling would make trying to do any cohesive state management
> strategy on the connections just about impossible, and would also
> effectively render any SQLA pool size settings rather meaningless.
>
> On Fri, Jan 23, 2009 at 12:51 PM, Michael Bayer
> <[email protected]>wrote:
>
>
>
> > I believe this is a setting you establish when you create the DSN
> > yourself, no ?
>
> > On Jan 23, 2009, at 12:27 PM, Rick Morrison wrote:
>
> > > > To make pyodbc close the connection is settine pyodbc.pooling =
> > > False.
>
> > > Whoa, I didn't know pyodbc automatically used ODBC connection
> > > pooling. Seems like we should be turning that off if the user is
> > > using SQLA pooling.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
