On Thu, Nov 14, 2013 at 5:50 PM, Danny Gorton
wrote:
> However, that shouldn't really affect what you're doing much since we're
Yeah, I just like to hear what are others doing and thinking.
> also not considering updating the Firebird provider at this time either.
> The version we have seems t
Thanks for the info Juri. I failed to mention that we're a
cross-platform solution, with Linux being the main one, so I'm more
concerned with compatibility on Mono than on Windows. It will just
require some test cycles we don't have right now.
However, that shouldn't really affect what you're
On Thu, Nov 14, 2013 at 11:46 AM, Zvjezdan Tomičević wrote:
> Polling with default value
I'm asking to know what "resolution" should the cleanup routine have.
Like if everybody uses lifetime 10s, than resolution 5s is fine, even
10s is fine, though the connection might be in a pool little longer.
I use firebird heavily in sports betting solution, with many simultaneous
connections, in desktop environment, web services and virtually everywhere.
Current deployed version is 2.6.0.0, 3.5 build. No major problems here at
all.
Polling with default value,and for events no polling.
Since DB is hit
And just a one quick "research" question. What's your common
connection lifetime value for pooling? Do you change it or do you use
the default one?
--
Jiri {x2} Cincura (x2develop.com founder)
http://blog.cincura.net/ | http://www.ID3renamer.com
-
Hi,
On Wed, Nov 13, 2013 at 8:34 PM, Danny Gorton
wrote:
> If 4.0 backward compatibility is
> OK, then it would be OK
It's probbaly not 100%, but in case you're not relying on some "weird"
behavior you found, you should be OK. You can read:
http://msdn.microsoft.com/en-us/library/ee941656%28VS.1
