> > The code is committed at separate branch: > > > > https://github.com/FirebirdSQL/firebird/tree/timeouts > > > > Documentation is there: > > > > > > > https://github.com/FirebirdSQL/firebird/blob/timeouts/doc/README.state > > ment_timeouts > > > > > > https://github.com/FirebirdSQL/firebird/blob/timeouts/doc/README.sessi > > on_idle_timeouts > > > > If there will be no objections i plan to merge it into master next week. > > Done, testers are welcome ;)
Unfortunately, I doubt that the feature as implemented has any benefits for our applications. We have a number of our clients that access our databases via ODBC/JDBC connections to perform data extract. These connections perform only a few heavy weight SQL statements (taking max 3-4 of real execution time). Most of the time is spent in the Firebird engine waiting for the next fetch, due to network latencies. Some of these extract functions/statements run for 60+ minutes. Without the ability to not have time "waiting for fetch" not included in the timeout, we would need to set default timeout value so high (ie. 90 minutes) that the real benefit of preventing/stopping "run away/stupid" queries would be completely lost -- even with the ability to set timeout on a connection or transaction basis. Sean ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
