You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for an excellent module. I have one fairly simple quetion. If a query is executed that returns a large amount of data, is the data collected in memory in its entirety before the query call returns? Alternatively, are rows and/or result sets made available to the caller as they are received? Essentially I would like to stream results, and am not sure if I should divide the large query into chunks, or just let the driver deal with it. For a little more clarity, suppose https://github.com/denisenkom/go-mssqldb#reading-output-parameters-from-a-stored-procedure-with-resultset returns 1 million rows. Would the first rows.Scan execute prior to all data being received? Thanks
The text was updated successfully, but these errors were encountered:
TDS, the protocol, streams results back row by row, result set by result
set.
The query itself may require finishing prior starting any return, such as a
TOP 10 query or an ORDER BY query.
Thank you for an excellent module. I have one fairly simple quetion. If a query is executed that returns a large amount of data, is the data collected in memory in its entirety before the query call returns? Alternatively, are rows and/or result sets made available to the caller as they are received? Essentially I would like to stream results, and am not sure if I should divide the large query into chunks, or just let the driver deal with it. For a little more clarity, suppose https://github.com/denisenkom/go-mssqldb#reading-output-parameters-from-a-stored-procedure-with-resultset returns 1 million rows. Would the first rows.Scan execute prior to all data being received? Thanks
The text was updated successfully, but these errors were encountered: