SCM

[#1011334] NpgsqlConnection.GetSchema doesn't dispose connections

View Trackers | Bugs | Download .csv | Monitor

Date:
2013-05-27 17:32
Priority:
3
State:
Closed
Submitted by:
Francisco Figueiredo jr. (fxjr)
Assigned to:
Shay Rojansky (roji)
Npgsql Version:
None
Category:
None
Group:
None
Resolution:
Accepted
Summary:
NpgsqlConnection.GetSchema doesn't dispose connections

Detailed description
From https://github.com/franciscojunior/Npgsql2/issues/9
github user: mfenniak


Hi,

I noticed that NpgsqlConnection.GetSchema will, for some cases, create a new NpgsqlConnection using the same connection string. In these cases, the new connection is never disposed. I think these connections should be wrapped in using block to prevent this case.

Mathieu

Followup

Message
Date: 2013-09-29 21:37
Sender: Shay Rojansky

Proposed pull request: https://github.com/franciscojunior/Npgsql2/pull/63

Attached Files:

Changes:

Field Old Value Date By
status_idOpen2013-10-02 18:12roji
close_dateNone2013-10-02 18:12roji
ResolutionNone2013-10-02 18:12roji
assigned_tonone2013-09-28 15:45roji
details From https://github.com/franciscojunior/Npgsql2/issues/9 github user: mfenniak Hi, I noticed that NpgsqlConnection.GetSchema will, for some cases, create a new NpgsqlConnection using the same connection string. In these cases, the new connection is never disposed. I think these connections should be wrapped in using block to prevent this case. Mathieu2013-09-28 15:45roji
Powered By FusionForge