lidavidm commented on issue #64: URL: https://github.com/apache/arrow-adbc/issues/64#issuecomment-1215574770
JDBC/ODBC and Flight SQL/Go are unfortunately at odds here, though. I'm not sure if there's a great way to express that Flight SQL lets you do this without penalty without also penalizing the JDBC/ODBC case. JDBC/ODBC wrappers could also potentially lazily materialize; a second call to Execute() would force the original result set to be materialized before executing the new query. This would mean the driver has to manage that synchronization itself. -- 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]
