Do we want something more flexible than dlopen() and runtime symbol lookup (a mechanism which constrains the way you can organize and distribute drivers)?
For example, perhaps we could expose an API struct of function pointers that could be obtained through driver-specific means.
Le 26/04/2022 à 18:29, David Li a écrit :
Hello, In light of recent efforts around Flight SQL, projects like pgeon [1], and long-standing tickets/discussions about database support in Arrow [2], it seems there's an opportunity to define standard database interfaces for Arrow that could unify these efforts. So we've put together a proposal for "ADBC", a common Arrow-based database client API: https://docs.google.com/document/d/1t7NrC76SyxL_OffATmjzZs2xcj1owdUsIF2WKL_Zw1U/edit#heading=h.r6o6j2navi4c A common API and implementations could help combine/simplify client-side projects like pgeon, or what DBI is considering [3], and help them take advantage of developments like Flight SQL and existing columnar APIs. We'd appreciate any feedback. (Comments should be open, please let me know if not.) [1]: https://github.com/0x0L/pgeon [2]: https://issues.apache.org/jira/browse/ARROW-11670 [3]: https://github.com/r-dbi/dbi3/issues/48 Thanks, David
