Hi *,
I just found behavior that surprised me. Suppose pooling is on and
(all connections to same database):
Open connection1.
Open connection2.
Close connection2.
FbConnection.ClearAllPools();
Try to use connection1.
On this ^ line you'll get exception as the connection1 was also
cleared aka
ClearAllPools should not close/dispose open connections.
A function to close all pooled connections might be useful however for when
you need to close all connections maybe with different name like
CloseAllPooledConnections
On Wed, Apr 17, 2013 at 10:29 AM, Jiri Cincura disk...@cincura.net
On Wed, 17 Apr 2013 10:29:57 +0200, Jiri Cincura disk...@cincura.net
wrote:
Hi *,
I just found behavior that surprised me. Suppose pooling is on and
(all connections to same database):
Open connection1.
Open connection2.
Close connection2.
FbConnection.ClearAllPools();
Try to use
On this ^ line you'll get exception as the connection1 was also
cleared aka closed/disposed. I always used ClearAllPools with all
connections closed so I had no idea it behaves like that.
Interesting, I also never noticed.
But do you think is correct? Should the ClearAllPools clear even the
Why NETProvider-1.7.2 does not work with Firebird Embedded 2.5?
Key: DNET-496
URL: http://tracker.firebirdsql.org/browse/DNET-496
Project: .NET Data provider
Issue Type: Bug
.Net provider Generates Outer aplly statement
---
Key: DNET-497
URL: http://tracker.firebirdsql.org/browse/DNET-497
Project: .NET Data provider
Issue Type: Bug
Components: Entity
Hello all,
I'm trying to update an application that uses Factories from version 2.1 to
3.0.2 of the provider.
I've registered the dll in the gac by using gacutil.exe from VS2010 command
line. This is the output of /l option:
FirebirdSql.Data.FirebirdClient, Version=3.0.2.0, Culture=neutral,
