zeroshade commented on issue #64: URL: https://github.com/apache/arrow-adbc/issues/64#issuecomment-1215400906
> I am only talking about a single query, so this is sort of irrelevant to Go. For Go, I would expect each call to Query to initialize and use a new AdbcStatement, at which point it would be up to the driver to manage concurrency. Does that sound reasonable? So, if a consumer hasn't picked up *all of the results* from a call to a prepared statement before executing it again, they will lose any remaining results? That seems difficult to enforce or otherwise prevent a user from doing. Is there a reason we can't keep the `ArrowArrayStream*` result set as independent? For example, using a prepared statement to query, then handing the result stream off to another thread to consume while exeucting it again with different arguments. (FlightSQL would support this easily since each execution would be a separate `FlightInfo` ticket) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
