Hi, I suspect that what I am doing with Exposed (0.31) is leaking memory and/or resources. Are there ways to disable all of Exposed's caching? What are tools to detect improper use of the Exposed DAO?

why do you think there is a leak? Can't see the code with DAO

I think there is a leak because over time anything I do against the database is slow and my program uses a lot of memory. I am not saying this is an issue in Exposed per se. I am just looking for a way to disable caching to quickly eliminate it from the list of possible causes

what kind of caching? In your examples, there is no Entity exposed (only they are cached), therefore there is nothing to disable

I haven't posted any examples

most likely you are doing a lot of transactions

yes, and?

I haven't posted any example

how difficult. are you using Entity?

if transactions are in some way postponed and eventually pile up then I'd like to hear how to disable that.

transactions impose restrictions on, for example, table entries. It is not possible in an RDBMS to write to one table from different threads (transactions) https://en.wikipedia.org/wiki/Database_transaction https://www.tutorialspoint.com/dbms/dbms_transaction.htm

@edwinRNDR, there can be diferrent type of leaks: connection leak, prepared statement leak, resultset leak, etc, what kind of do you have? Entity Cache is bound to transaction and memory should be free after the end of transaction block.