SCM

[#1010466] Npgsql isn't using pool when executing under Mono

View Trackers | Bugs | Download .csv | Monitor

Date:
2008-09-08 13:57
Priority:
3
State:
Closed
Submitted by:
Francisco Figueiredo jr. (fxjr)
Assigned to:
Nobody (None)
Npgsql Version:
None
Category:
Group:
Resolution:
None
Summary:
Npgsql isn't using pool when executing under Mono

Detailed description


It seems that under Mono, Npgsql isn't using Mono. It seems it is related to connectionbuildstring not enabling the pool setting even when it is set to true.

Also, under Mono the connection doesn't seem to be being returned to pool correctly. It seems to be using Connection.ConnectionString as the key to get the connection pool hash table and Connector.ConnectionString as the key to return it back. Those two properties are supposed to be the same but for some reason, the ToString() value returned by them to create the key seems to be somehow modified. For exemple:

Connection.ConnectionString = server=blahblah;password=blahblah;pooling=true;

Connector.ConnectionString = server=blahblah;pooing=true;password=blahblah;


This also raises the issue of the motivation of having ConnectionString on NpgsqlConnection object and on NpgsqlConnector. But this is another issue.




Followup

Message
Date: 2008-12-18 00:22
Sender: Jon Hanna

Closing since the last release notes says this very bug is fixed!

Attached Files:

Changes:

Field Old Value Date By
status_idOpen2008-12-18 00:22talliesin
close_date2008-12-18 00:222008-12-18 00:22talliesin
Powered By FusionForge