The final touches to RowSet

Not too late the letter came. The burden of the message was «Faster!». We suppose It is time to review a meaning of this term.

Changes of IBProvider commercial version

• The dynamic cache of numbers of result set. IBProvider initializes the cache gradually. Cache maximum size can be indicated through a property of rowset «Memory Usage«. It results in selection of memory only for a really used part of the cache. Earlier cache at once initialized all memory, indicated to it, that resulted in slow start and superfluous usage of such precious resource as Memory.
• Use of the hash-table to manage the cache. It allows effectively to control the cache for very large number of rowset of result set. Earlier cache managing expenses were proportional it to the size. Again see property «Memory Usage«.
• 64-bit access to the temporary file.
• The 32-bit cache of rowset. 16-bit indexation was used earlier, therefore top bound of number of rowset in the cache was 65535.
• Fast loading of result set. When positioning in the end of set and skipping of row record immediately in the temporary file is made, passing the cache. As the corollary — Memory is not allocated.
• The new parameter for line of connection — «bicursor«. It allows to set operational mode of cursors of result sets by default — one-direction or random-access. By default the first variant is kept.