lidavidm commented on issue #64: URL: https://github.com/apache/arrow-adbc/issues/64#issuecomment-1214418597
Thanks, I think that aligns with what I am basically assuming so far: no concurrent access (though maybe a particular driver can relax this, e.g. Flight SQL), but also no guarantees on thread identity (I think some APIs call this "serialized" access). I think the main thing will be to either define that concurrent statements cannot be created from the same connection (may be overly restrictive, especially for Flight SQL), or that they cannot necessarily be used concurrently. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
