On Monday, February 24, 2020 at 6:23:32 PM UTC-5, Mike Bayer wrote:
>
> it looks like garbage collection.   SQLAlchemy 2.0 won't do that, it will 
> just warn that you left a connection open somewhere.   we would hope that 
> the SQLite gc routine doesn't raise like that.
>

Thanks Mike, this helped immensely.

I traced this to happening somewhere in the interplay of 
pyramid/pyramid_tm/transaction.  It only seems to happen on the first 
request, and seems to be an artifact of the testing environment *before* i 
get to close my connections. 

-- 
SQLAlchemy - 
The Python SQL Toolkit and Object Relational Mapper

http://www.sqlalchemy.org/

To post example code, please provide an MCVE: Minimal, Complete, and Verifiable 
Example.  See  http://stackoverflow.com/help/mcve for a full description.
--- 
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 sqlalchemy+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sqlalchemy/573fe520-2ceb-4b0c-aa35-510f3af330c1%40googlegroups.com.

Reply via email to