zeroshade commented on issue #2040: URL: https://github.com/apache/arrow-adbc/issues/2040#issuecomment-2305242075
The Python ADBC bindings tend to use the regular statement workflow rather than Prepared statements as a performance / safety scenario to ensure compatibility with DBAPI and parameter binding, while also allowing an easier workflow for users and reducing code duplication in the bindings. The native implementations (the actual ADBC spec, the Go implementation, C# impl, etc.) expose the lower level constructs which allow users to make the decision themselves whether or not they call `Prepare`. So those implementations won't use the `Prepare` workflow unless a user explicitly calls the `StatementPrepare` / `Statement.Prepare` functions -- 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]
