paleolimbot commented on issue #1398: URL: https://github.com/apache/arrow-adbc/issues/1398#issuecomment-1867862161
It should also be said that the fact that SQL generation is so closely linked to driver implementations *might* be R-specific: dbplyr is the only SQL generator in town and it dispatches a number of things on the class of the "driver", which it assumes is a DBI driver. Some backend-specific behaviour is hard-coded in dbplyr and other parts dispatch on the driver class. I'm not all that familiar with how it works in Python, but I think Python's SQL generation game is not coupled with `dbapi` in quite the same way or at all. This is arguably a much better design and it may be that improving the ecosystem on the R side is a more worthwhile exercise than codifying driver quirks in a C-stable API. I imagine that even with an improved ecosystem, we'll need *something* from the driver beyond an info string. I wonder if something like `AdbcConnectionCallMethod(AdbcConnection*, const char* method_name, ArrowArrayStream* input, ArrowArrayStream* output);` could mitigate the need for adding functions to the header. -- 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]
