You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the issue @taozuhong. Could you sketch out what sequence of commands you might like to see? And maybe show us what you're going now so we can compare. Or, do you have any examples where language-independent package managers (like dbc) do this?
Having dbc install a driver manager and client library is possible but somewhat tricky to get right. It's easier in some languages, like .NET or Ruby, but harder languages like Python or R where people use a variety of package managers and project metadata files.
Thanks. Installing multiple drivers in one command is on our roadmap, see #277.
You can install drivers to a specific location by setting the ADBC_DRIVER_PATH to that location before running dbc commands like install. So you should be to do what you need here. Note that any applications you're using that use a driver manager need to also set the same environment variable to see the drivers you install this way.
For example,
set ADBC_DRIVER_PATH=somewhere_in_msys2
dbc install flightsql
Activity
amoeba commentedon Sep 11, 2026
Thanks for the issue @taozuhong. Could you sketch out what sequence of commands you might like to see? And maybe show us what you're going now so we can compare. Or, do you have any examples where language-independent package managers (like dbc) do this?
Having dbc install a driver manager and client library is possible but somewhat tricky to get right. It's easier in some languages, like .NET or Ruby, but harder languages like Python or R where people use a variety of package managers and project metadata files.
taozuhong commentedon Sep 12, 2026
I like the follow command:
dbc install --env <user/msys-ucrt64/msys-mingw64/?> <base/flightsql/sqlite/postgresql>
BTW, install command could add target path to replace default install path?
amoeba commentedon Sep 12, 2026
Thanks. Installing multiple drivers in one command is on our roadmap, see #277.
You can install drivers to a specific location by setting the
ADBC_DRIVER_PATHto that location before running dbc commands like install. So you should be to do what you need here. Note that any applications you're using that use a driver manager need to also set the same environment variable to see the drivers you install this way.For example,
Then in a program,
This is explained in https://docs.columnar.tech/dbc/guides/installing/#adbc_driver_path.
Does that help?
Making the dbc and the ADBC driver managers msys2 aware hasn't come up yet so it's certainly something we can think about.