> > it is the value that represent a direct CPU cost of a SQL statement. > > You actually seem wanting CPU quotas. But they're not timeouts. A long- > running statement may produce almost zero CPU load.
I have no problem with "ExecutionQuota" describing the functionality that I am referring to. I do think, however, that the implementation of the quota is within reach, only requiring small/modest additions to the timeouts that Vlad has implemented. 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