Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

discuss ADBC_DRIVER_PATH path list behavior

Aperta
  • Qualcosa non va?
#61 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
35/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
go
Ambito
cli, documentation

Direzione di ricerca

Start with the Installing guide's ADBC_DRIVER_PATH section, which the issue names, and compare its description with the install example in the issue. The issue also raises a behavior question about skipping nonexistent paths, but gives no decision or implementation entry point. Done for the documentation task means explaining the current behavior; any behavior change depends on discussion resolving what it should be.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

question

There's an asymmetry in how dbc treats ADBC_DRIVER_PATH compared to the driver managers. I'd like to point it out and discuss whether we should change the behavior.

ADBC_DRIVER_PATH can be a path list and, when it is, the driver manager will search the paths (in order) for a matching manifest. This means that, for example, the first path can be entirely non-existent and it will be effectively skipped.

dbc handles this differently. Instead of checking whether a path in the past list exists, it will create it and install from there. I'm not yet sure what our uninstall behavior is.

I see this as an asymmetry that might be confusing. I also think it means that dbc doesn't really support path lists in ADBC_DRIVER_PATH. For example, this,

$ mkdir "$HOME/does_exist"
$ export ADBC_DRIVER_PATH="$HOME/does_not_exist:$HOME/does_exist"
$ echo $ADBC_DRIVER_PATH 
/home/bryce/does_not_exist /home/bryce/does_exist
$ go run ./cmd/dbc install mysql
[✓] searching
[✓] downloading
[✓] installing
[✓] verifying signature

Installed mysql 0.1.0 to /home/bryce/does_not_exist

(Notice that it installs to does_not_exist)

is the same as if I hadn't set the path list at all,

$ export ADBC_DRIVER_PATH="$HOME/does_not_exist"

Should dbc check if the path exists before trying to use it and otherwise skip over it?

Tasks:

  • Discuss
  • Update docs, particularly the Installing guide's ADBC_DRIVER_PATH section to describe the behavior
Lingua principale
Go
Stelle
154
Fork
15
Merge medio
2g 12h
PR unite (30g)
25

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di columnar-tech/dbc

Tutte le issue di columnar-tech/dbc

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.