What happens with SQLite temp tables in a connection pooling scenario? Can ASP.NET/ADO.NET connection pooling keep a SQLite connection (and any temp tables associated with it) alive so that when user # 2 grabs a connection, it might find that temp tables not explicitly dropped by user #1 already exist? I know how to test for existence of a table in SQLite syntax -- I'm just not clear about the connection's lifetime and scope is ASP.NET.
Thanks