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