Uma i-pip ithola ibm_db kodwa ukufakwa komthombo kwehluleka ngesikhathi kulandwa i-clidriver, hlela futhi isicelo se-urllib seskripthi sokwakha. I-proxy argument enikezwe i-pip kuphela ayihleli zonke izilayishi zezingane.

Ngaphambi kokuqala ukufakwa komthombo kusuka ku-shell ye-POSIX:

export https_proxy=http://proxy.example.net:8080
export http_proxy=http://proxy.example.net:8080

Isiphathi se-proxy esizenzakalelayo se-urllib sisebenzisa lezi zinto eziguquguqukayo kuma-scheme wendawo eziwukufika. Gcina okuhlukile kwe-no_proxy kuhambisana nokufinyelela kumsingathi wedrayiver. Uma ukulanda kwedrayiver yomphakathi kungadlula kwabalamuli bomphakathi, uhlu lwe-proxy ye-HTTP lunikeza abazakheli balezi zindawo ze-URL.

Gcina i-URL ehlulekile kusuka kokuphuma kokwakha. Ukwenqatshwa kokulanda kwe-clidriver kwenzeka ngaphambi kokusethwa koxhumano lwe-Db2 futhi akulungiswa ngentambo yoxhumano lwesizindalwazi.

Ukulanda okungeziwe kuncike endleleni yokufaka. Amasondo ahambisanayo noma idrayiver yasekhaya enikezwe ngamabomu kungashintsha okulandwayo. Ekwakhiweni komthombo okusekelwayo okusebenzisa idrayiver ekhona, i-IBM_DB_HOME isho indawo yayo yokufaka enezihloko namalabhulali adingekayo; indawo engenalutho ayinikezi lutho kukho.

Izihloko ezihlobene