Vlad,
> Documentation is there: > > https://github.com/FirebirdSQL/firebird/blob/timeouts/doc/READM > E.statement_timeouts > > https://github.com/FirebirdSQL/firebird/blob/timeouts/doc/READM > E.session_idle_timeouts > > If there will be no objections i plan to merge it into master next week. I am concerned about the implementation. If I read the documentation correctly, a statement which performed (say) a SELECT against a table that follows a NATURAL scan, which is 'paused' awaiting the next Fetch, would run into the timeout, even though there is no "cost" to the engine of waiting. Am I correct? Separately, it would be "a good thing" if the Timeouts could be set in Trigger or SP -- perhaps via special "SQL_Timeout" RDB$Context for the "User_Session" and "User_Transaction" namespaces. 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
