Re: [Firebird-net-provider] Database triggers

2012-04-16 Thread Jiri Cincura
And there's another one. What about connection pooling? :) The pool is currently based on connection string. So if you open connection with .Open(suppressTrigger: true) and later call .Open(suppressTriggers: false) you'll get wrong behavior. I can extend the pool to take into account this "special

Re: [Firebird-net-provider] fbembed.dll DllNotFoundException exception

2012-04-16 Thread Jiri Cincura
Do you have C++ runtime on that machine? The msvc.dlls? -- Jiri {x2} Cincura (x2develop.com founder) http://blog.cincura.net/ | http://www.ID3renamer.com -- Better than sec? Nothing is better than sec when it comes to mon

[Firebird-net-provider] fbembed.dll DllNotFoundException exception

2012-04-16 Thread Steve Harp
Hi Guys, I'm using Firebird.Data.FirebirdClient.dll version 2.6.5.0 and fbembed.dll version 2.5.1.26351 with a .NET v4.0 c# application. It works fine on my development machine but when I install on a target Windows XP box I get an error "System.DllNotFoundException: Unable to load DLL 'C:\Prog

Re: [Firebird-net-provider] Database triggers

2012-04-16 Thread Gerdus van Zyl
On Mon, Apr 16, 2012 at 3:11 PM, Jiri Cincura wrote: > On Wed, Apr 11, 2012 at 1:37 PM, Gerdus van Zyl > wrote: >> I would prefer it on the FbConnection.Open method. >> It would then be like transaction options and >> Connection.BeginTransaction. The connection string thus remains >> uncomplicat

Re: [Firebird-net-provider] Database triggers

2012-04-16 Thread Ivan Arabadzhiev
One more vote for the .Open method. I think it`s quite firebird-specific and therefore has no place in the connection string. > On Wed, Apr 11, 2012 at 1:50 PM, Mercea Paul > wrote: >> As i remember well there is a option on restore proces to start without >> activating database triggers. >

Re: [Firebird-net-provider] Database triggers

2012-04-16 Thread Jiri Cincura
On Wed, Apr 11, 2012 at 1:37 PM, Gerdus van Zyl wrote: > I would prefer it on the FbConnection.Open method. > It would then be like transaction options and > Connection.BeginTransaction. The connection string thus remains > uncomplicated. OTOH the default (generic) isolation level can be specifie