Re: [Firebird-net-provider] Database triggers

2012-04-17 Thread Ivan Arabadzhiev
I agree on that one - Open(triggers=false) should imply 'pooling=false' in the connection string. That way it will not pollute the pool (if it is used) and no further handling will be needed. > Well suppressTriggers is not something you would routinely use so I think > it should bypass connect

Re: [Firebird-net-provider] Database triggers

2012-04-17 Thread Gerdus van Zyl
Well suppressTriggers is not something you would routinely use so I think it should bypass connection pooling. On Tue, Apr 17, 2012 at 8:00 AM, Jiri Cincura wrote: > And there's another one. What about connection pooling? :) > > The pool is currently based on connection string. So if you open >

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] 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

Re: [Firebird-net-provider] Database triggers

2012-04-11 Thread Jiri Cincura
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. AFAIR on gbak/nbackup only, isn't it? This doesn't apply to ServicesAPI. -- Jiri {x2} Cincura (x2develop.com founder) http://blog.cincur

Re: [Firebird-net-provider] Database triggers

2012-04-11 Thread Mercea Paul
Hi Jiri Second vote to put in Open method. As i remember well there is a option on restore proces to start without activating database triggers. On 2012.04.11 11:42 AM, Jiri Cincura wrote: > Hi *, > > I started working on option to disable database triggers (DNET-312) > when connecting to datab

Re: [Firebird-net-provider] Database triggers

2012-04-11 Thread Gerdus van Zyl
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. On Wed, Apr 11, 2012 at 10:42 AM, Jiri Cincura wrote: > Hi *, > > I started working on option to disable database trigger

[Firebird-net-provider] Database triggers

2012-04-11 Thread Jiri Cincura
Hi *, I started working on option to disable database triggers (DNET-312) when connecting to database. But I'm not sure how to expose it in API. I thought about A) in connection string B) in FbConnection.Open method The connection string seems to me to be more ADO.NET-ish way, though the Open met