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 <disk...@cincura.net> wrote:
> 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" settings, but even that,
> if you do .Open(suppressTriggers: false) and then again
> .Open(suppressTriggers: false), the trigger will be actually invoked
> only once. :\ Seems to me like hidden magic.
>
> Ideas?
>
> --
> 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
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Firebird-net-provider mailing list
> Firebird-net-provider@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider