Two settings named 'http_proxy' #13880
Description
What happens?
There are two settings named 'http_proxy' :
| name | value | description |
|---|---|---|
| http_proxy | 127.0.0.1:8999 | HTTP proxy host |
| http_proxy_username | Username for HTTP proxy | |
| http_proxy | Password for HTTP proxy | |
| http_logging_output | The file to which HTTP logging output should be saved, or empty to print to the terminal |
To Reproduce
D select name, value, description from duckdb_settings() where name like 'http%';
| name | value | description |
|---------------------|-------|------------------------------------------------------------------------------------------|
| http_proxy | | HTTP proxy host |
| http_proxy_username | | Username for HTTP proxy |
| http_proxy | | Password for HTTP proxy |
| http_logging_output | | The file to which HTTP logging output should be saved, or empty to print to the terminal |
D set http_proxy to '127.0.0.1:8999' ;
D select name, value, description from duckdb_settings() where name like 'http%';
| name | value | description |
|---------------------|-----------------------|------------------------------------------------------------------------------------------|
| http_proxy | 127.0.0.1:8999 | HTTP proxy host |
| http_proxy_username | | Username for HTTP proxy |
| http_proxy | | Password for HTTP proxy |
| http_logging_output | | The file to which HTTP logging output should be saved, or empty to print to the terminal |
OS:
Windows 10 x86_64
DuckDB Version:
v1.1.0 fa5c2fe
DuckDB Client:
CLI
Hardware:
No response
Full Name:
Phil Leach
Affiliation:
Bloomberg
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a nightly build
Did you include all relevant data sets for reproducing the issue?
Yes
Did you include all code required to reproduce the issue?
- Yes, I have
Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?
- Yes, I have