[sqlalchemy] Re: Full connection pool close

[Smoke]

On 23 Gen, 21:24, Rick Morrison <rickmorri...@gmail.com> wrote:
> > OK, it should use whatever is set on the ODBC DSN then.   im not sure that
> > pyodbc should have an opinion about it.
>
> Eh?
>
> > is there a way to set pyodbc.pooling = None or some equivalent ?
>
> It's pyodbc.pooling = False, as appears many times upthread
>
> From the OP's description, it sounds like SA is somehow not forcefully
> closing the DBAPI connection (perhaps not disposing of the connection using
> del).

it's seems that it's not using close() at all, because my connection
was closed before doing "del con"...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to 
sqlalchemy+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---