lidavidm commented on issue #64: URL: https://github.com/apache/arrow-adbc/issues/64#issuecomment-1215342377
> Are we referring to result sets from _different queries_ or only putting a limitation on result sets from a single prepared statement? So to be clear, "statement" here refers to any query, since there is a separate structure (`AdbcStatement`) to hold query state. (This is analogous to JDBC/ODBC Statement, or DBAPI Cursor.) 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? If we add the one-shot `Query` to ADBC itself, it would have the same semantics as creating an independent `AdbcStatement` for each call. > While the prepared statement can be used by multiple goroutines, it will not be used concurrently by those goroutines. Basically the database/sql package's sql.Stmt object is safe for concurrent use, but it internally ensures serialization to it's calls to the underlying Driver's driver.Stmt object. It is, however, bound to a single Connection object. Thanks - so, basically consistent with every other API then. -- 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
