Devart Forums

I have the same problem with the latest dotConnect for Postgres. It has been an issue for about the last 5 releases of dotConnect for Postgres. I always thought it was a problem with me environment.

Thanks,

Charlie J.

So is this fix in dotConnect for PostgreSQL as well or just LinqConnect?

Thanks,

Charlie J.

Thanks. The closing of the connections seem to be working. We are verifying that it is actual reusing connections from the pool.

Thanks,

Charlie J.

Thanks. I will do that. Is this built on the top of the latest dotConnect for PostgreSQL 5.50.228? Does it contain the following fix as well? The bug with assigning the UnpreparedExecute option from connection string to the command is fixed


Thanks,

Charlie J.

Thanks Shalex.

Does dotConnect for PostgreSQL 5.50.228 contain the connection pooling fix using SSPI/GSS authentication?

If not, please send the internal build with the fix to [email protected]

Thanks,

Charlie J.

I am able to close the connection by overriding the dispose method for my EF Context. But I dont know if this is the best and safe way to do it.

protected override void Dispose(bool disposing)
{
Devart.Data.PostgreSql.PgSqlConnection.ClearAllPools();
//Devart.Data.PostgreSql.PgSqlConnection.ClearPool((PgSqlConnection)((EntityConnection)this.Connection).StoreConnection);

base.Dispose(disposing);
}

Thanks,

Charlie J.

Any updates on When will the UnpreparedExecute connection string parameter function the same way without put this workaround in the constructor of the EF Context?

Thanks,

Charlie J.

With the internal build, GSS finally works in our environment. But there are things that stopped working.


1.) Unprepared Execute = true in the connection string doesn't work. When I look at my Postgres logs, all statements are being prepared and performance is real bad.

[Correction]
The Unprepared Execute = true does work if you also set Devart.Data.PostgreSql.Entity.PgSqlEntityProviderServices.UnpreparedCommandExecution = true; in code. There is an issue with using DBProviderFactory setting this. Please see the following link for more details: http://www.devart.com/forums/viewtopic. ... s&start=45



2.) Max Pool doesnt work. Connections in the Pool are not being reused. A new connection is being created each time exceeding Max Pool.

Thanks,

Charlie J.

With the internal build, GSS finally works in our environment. But there are things that stopped working.

1.) Unprepared Execute = true in the connection string doesn't work. When I look at my Postgres logs, all statements are being prepared and performance is real bad.

2.) Max Pool doesnt work. Connections in the Pool are not being reused. A new connection is being created each time exceeding Max Pool.

Thanks,

Charlie J.

PatrickG is correct. I am having the same problem. It is very easy to reproduce. I am using SSPI/GSS integrated security in my connection string and it is creating a new connection each time.

Thanks,

Charlie J.

I have sent our license information this we can obtain the internal build that contains the GSS fix. Please email the internal build to [email protected].


Thanks,

Charlie J.

Done. The email has been sent containing the license information requested.

Looking forward to trying out the complete internal build that contains the GSS fix.

Thanks,

Charlie J.

No problem. My manager will email you the information requested. Can I use assembly redirection to use the test assemblies that were email to me to work with my current installed version? Or does it have to be an internal build with the fix? We have the latest dotConnect for PostgresSQL 5.50 installed.

Thanks,

Charlie J.

Thanks. The test assemblies you send me did allow us to log in. But we get this error message after we log in

Schema specified is not valid. Errors:
DevPriceBook.ssdl(2,105) : error 0004: Could not load file or assembly 'Devart.Data.PostgreSql.Entity, Version=5.30.210.0, Culture=neutral, PublicKeyToken=09af7300eec23701' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Can you send your a complete package build with this fix in it? We are currently using the latest dotConnect for Postgres 5.50

Please email it to [email protected]

Thanks,

Charlie J.

Hi,

I did not receive an email with the new test assemblies. Please email it to [email protected]


Thanks,

Charlie J.