In a testing suite I have a fixture that drop all the tables in an engine,
then start fresh and create all the tables. After this fixture logic, my
test case runs, using the newly created table.
The fixture and the test case are run in the MainThread, while the database
consumer is a web applic
Thanks.
Do you have a minimalistic example on the lifecycle of table objects? Or
best practices of create, use, and destroy them?
How do we identify if they are continuously created and not destroyed?
On Thursday, January 6, 2022 at 5:28:00 AM UTC-8 Mike Bayer wrote:
> 1.3.16 doesn't have a lot
cx-oracle SessionPool is used underlying that will probe connections on
checkout and recover. Hence, trying to disable SQLAlchemy invalidate pool.
Thanks!
On Monday, January 10, 2022 at 12:04:57 PM UTC-8 Mike Bayer wrote:
>
>
> On Mon, Jan 10, 2022, at 1:30 PM, Anupama Goparaju wrote:
>
> Thanks.