实体框架和数据库连接(Entity Frameworks and database connections)

 我正在调试Jaroslaw Kowalski提供者包装。 在调试它时，我发现实体框架在每次查询后关闭连接。 在与数据库的每次交互中，在应用程序的生命周期中，打开数据库连接，并在执行查询后关闭连接 
 
 我的问题是： 
 
 
 
 默认情况下，底层提供者是否执行连接池。 
 
 
 如果我提供自己的资源池，那么我将如何知道何时关闭连接。 目前我正在使用Thread.GetDomain（）。ProcessExit事件注册并在事件触发时关闭连接。 这种方法好吗？ 
 
 
 困扰我的事情是Entity Framework本身正在关闭连接。 所以我有点犹豫是否想要集中连接，或者在特殊情况下可能会导致问题。 

I was debugging Jaroslaw Kowalski provider wrappers. While debugging it I observed that the Entity Framework closes the connection after every query. On every interaction with database, during the lifetime of application, a database connection is opened and after performing the query the connection is closed
 
My questions are:
 
 
 
Whether the underlying provider do connection pooling by default.
 
 
If I provide my own pooling then how will I know when to close the connection. At the moment I am registering with Thread.GetDomain().ProcessExit event and closing the connection when the event fires. Is this approach good? 
 
 
The thing that is bothering me is that Entity Framework itself is closing the connection. So I am a little hesitant to pool the connection or it may cause problems in exceptional scenarios.

原文：https://stackoverflow.com/questions/1928172