Re: ADBC - OS-level driver manager

I definitely see the problem here: we don't currently provide a way for something like a Microsoft Excel or PowerBI or Tableau to use ADBC drivers without bundling all of the ones they want to support or requiring/embedding Python or R. I also see how this is a particular problem for Windows and Ma

Re: ADBC - OS-level driver manager

Ha—no, I was thinking of a special ADBC-specific environment variable, which would work irrespective of the OS. On Tue, Apr 23, 2024 at 21:38 Matt Topol wrote: > An environment variable like LD_LIBRARY_PATH perhaps? =p > > On Tue, Apr 23, 2024, 8:40 PM Ian Cook wrote: > > > What if the driver m

Re: ADBC - OS-level driver manager

An environment variable like LD_LIBRARY_PATH perhaps? =p On Tue, Apr 23, 2024, 8:40 PM Ian Cook wrote: > What if the driver managers respected an environment variable containing a > delimited list of driver search paths? I think that would get us closer to > having true system-level configurabil

Re: ADBC - OS-level driver manager

What if the driver managers respected an environment variable containing a delimited list of driver search paths? I think that would get us closer to having true system-level configurability while mostly avoiding surprises and inflexibility. Ian On Tue, Apr 23, 2024 at 8:22 PM David Li wrote: >

Re: ADBC - OS-level driver manager

I'd rather not hard code it directly into the manager, both because this may surprise applications that don't want it and would be inflexible for applications who are looking to use it, but providing an additional list of search paths that (say) Excel can configure + some platform-specific guida

Re: ADBC - OS-level driver manager

I wonder if there is a relatively simple way to solve this problem. The ADBC driver manager libraries already make it possible to dynamically load drivers, and I believe these libraries already allow the user to specify which driver to use by passing either a bare filename or a full file path. So

Re: ADBC - OS-level driver manager

The advantage to system-wide registration of drivers (however that's accomplished) is of course that it allows driver authors to provide a single installer or set of instructions for the driver to be installed without regard for different usage scenarios. So if Tableau and Excel can both use ODBC d

Re: ADBC - OS-level driver manager

Also, with ADBC driver implementations currently in flux (none of them has reached the "stable" status in https://arrow.apache.org/adbc/main/driver/status.html), it might be a disservice to users to implicitly fetch drivers from potentially outdated DLLs on the current system. Regards Ant

Re: ADBC - OS-level driver manager

Wenbo Hu 于2024年3月20日周三 22:03写道： > > Hi David, > > I've been working on xDBC with Arrow for a while. I have some thoughts on > ODBC. > > We connect to the DBMS in Arrow stream using Python through four > different methods: JDBC, ADBC, ODBC, and the Python DB client library. > Typically, ADBC is t

Re: ADBC - OS-level driver manager

I have given this some thought and discussed it with some colleagues at Voltron Data. Something like this could be valuable in managed environments where there is a need to centrally define data sources across a fleet of systems. Perhaps it would also be valuable for individual system-level configu

Re: ADBC - OS-level driver manager

> it seems like the current driver manager work has been largely targeting an app-specific implementation. Yup, that was the intention. So far discussions of ADBC having a system-wide driver registration paradigm like ODBC have mostly been to discuss how much we dislike that paradigm and would pre

Re: ADBC - OS-level driver manager

Hi David, I've been working on xDBC with Arrow for a while. I have some thoughts on ODBC. We connect to the DBMS in Arrow stream using Python through four different methods: JDBC, ADBC, ODBC, and the Python DB client library. Typically, ADBC is the preferred method as it provides a "native" way f

ADBC - OS-level driver manager

ODBC has different OS-level driver managers available on their respective systems. It seems like the current driver manager work has been largely targeting an app-specific implementation. Have there been any discussions of ADBC having