Virtuoso Backend: Optimize ODBC getCharData
Review Request #106467 - Created Sept. 17, 2012 and submitted
Only use 1 SQLFetchData command in most of the cases. Callgrind stats show that 67.5% of the time in this function is spent in the first SQLFetchData, and an additional 27% in the second SQLGetData. We can avoid some of this extra cost, by only calling the function once. I can change the size of the default buffer if required.
I suppose 100 is fine in most situations except for long literals which are rarely queried anyway. This looks good. Did tests show that the overall performance improves on the getData call?