zeroshade commented on issue #64:
URL: https://github.com/apache/arrow-adbc/issues/64#issuecomment-1215600926
@lidavidm Don't beat yourself up, it wasn't in the docs haha. I had to read
the actual source code to figure that out :smile:
--
This is an automated message from the Apache Git S
zeroshade commented on issue #64:
URL: https://github.com/apache/arrow-adbc/issues/64#issuecomment-1215593890
@lidavidm I was writing that response and hten stepped away for a meeting
and came back to all your comments haha. but TL;DR: looks like under the hood
the database/sql package in G
zeroshade commented on issue #64:
URL: https://github.com/apache/arrow-adbc/issues/64#issuecomment-1215591703
> In general, my understanding of most APIs is that prepared statements
aren't really set up to benefit concurrent execution, only repeated execution
from a single logical chain of
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
zeroshade commented on issue #64:
URL: https://github.com/apache/arrow-adbc/issues/64#issuecomment-1215277102
> An individual statement can be used multiple times, but result sets cannot
be read concurrently (that is: executing a statement invalidates prior result
sets)
Are we referr
