fix: add workaround for driver manager venv path bug (#102)

This works around a bug we identified with the 1.8.0 driver managers
when using virtual environments. They are supposed to locate drivers in
`$VIRTUAL_ENV/etc/adbc/drivers` but they look in
`$VIRTUAL_ENV/etc/adbc/`. There may be a patch release soon to fix this
but, in the mean time, we can work around this by symlinking manifests
from `$VIRTUAL_ENV/etc/adbc/drivers` to `$VIRTUAL_ENV/etc/adbc/`. The
manifests use absolute paths so it's fine.

This PR also adds an integration workflow which is how I tested my
change. I don't think we want to run it on every single commit to the
repo so we might discuss here when we might want to run something like
this or if we want to run it in another repo.

Author: amoeba

.github/workflows/integration.yml

@@ -0,0 +1,60 @@
+# Copyright 2025 Columnar Technologies Inc.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+name: Integration
+
+on:
+  push:
+    branches:
+      - "main"
+  pull_request:
+
+concurrency:
+  group: ${{ github.repository }}-${{ github.head_ref || github.sha }}-${{ github.workflow }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+
+permissions:
+  contents: read
+
+jobs:
+  integration:
+    name: Build & Integrate (${{ matrix.os }})
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: ["ubuntu-latest", "macos-latest", "windows-latest"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install Go
+        uses: actions/setup-go@f111f3307d8850f501ac008e886eec1fd1932a34 # v5.3.0
+        with:
+          go-version: 1.24.2
+          cache: true
+          cache-dependency-path: go.sum
+
+      - name: Install Python
+        uses: actions/setup-python@v6
+        with:
+          python-version: "3.13"
+
+      - name: Build dbc
+        run: |
+          go build ./cmd/dbc
+        shell: bash
+
+      - name: Run Integration Tests
+        run: ./ci/scripts/run_integration.sh
+        shell: bash

ci/scripts/run_integration.sh

@@ -0,0 +1,17 @@
+#!/bin/sh
+
+set -eux
+
+python -m venv .venv
+
+if [ -f ".venv/bin/activate" ]; then
+  . ".venv/bin/activate"
+else
+  . ".venv/Scripts/activate"
+fi
+
+pip install adbc_driver_manager
+
+./dbc install duckdb
+
+python -c "from adbc_driver_manager import dbapi; dbapi.connect(driver=\"duckdb\");"

config/driver.go

@@ -171,12 +171,24 @@ func createDriverManifest(location string, driver DriverInfo) error {
 		}
 	}
 
-	f, err := os.Create(filepath.Join(location, driver.ID+".toml"))
+	manifest_path := filepath.Join(location, driver.ID+".toml")
+	f, err := os.Create(manifest_path)
 	if err != nil {
 		return fmt.Errorf("error creating manifest %s: %w", driver.ID, err)
 	}
 	defer f.Close()
 
+	// Workaround for bug in Python driver manager packages. Version 1.8.0 of the
+	// packages use the old ADBC_CONFIG_PATH path we originally had and not the
+	// new ADBC_DRIVER_PATH (e.g., /etc/adbc instead of /etc/adbc/drivers).
+	//
+	// To work around this, we create a symlink on level up to the manifest we're
+	// installing.
+	//
+	// TODO: Remove this when the driver managers are fixed (>=1.8.1).
+	symlink := filepath.Join(location, "..", driver.ID+".toml")
+	os.Symlink(manifest_path, symlink)
+
 	toEncode := tomlDriverInfo{
 		ManifestVersion: currentManifestVersion,
 		Name:            driver.Name,