From: Pavel C. <pc...@us...> - 2002-12-13 09:17:08
|
Sean, On 12 Dec 2002 at 19:48, Leyne, Sean wrote: > At this point, I think should remind everyone that the request was for > the *ability* to set a transaction timeout value. > > Nothing was ever said to suggest by enabling this feature, that the > engine would by 'default' start closeing connections. > > I think of this as equivalent to Nickolay's new explicit locking feature > in v1.5. It's there, if you don't want to use, fine no one is going to > force you to. but if it helps deal with a bad software/problem (maybe > you don't have the source), what's the harm? Well, but how about the code bloat and new potential points of failure ? The small footprint and compact code and behaviour is one from major FB features that are easy to lose, but hard to achieve. I have nothing against new features, if they are reasonable. For me, "reasonable" means (at least) one point from: 1) Satisfy a general requirement 2) Satisfy an occasional requirement of many that's hard to achieve by other ways effectively 3) Satisfy general requirement of few that's hard to achieve by other ways effectively The transaction timeout seems to fall in third category, but I'm not convinced that it's not doable effectively "outside the engine". Best regards Pavel Cisar http://www.ibphoenix.com For all your upto date Firebird and InterBase information |