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
When I trying to use DuckDB shell to add files with Chinese filenames and it's not working.
The webpage has crashed and is unresponsive.
But, DBeaver Client can normally read the same file without any issues.
Please Check.
To Reproduce
.files add
.files list
OS:
x86_64
DuckDB Version:
1.1.1
DuckDB Client:
shell
Hardware:
windows
Full Name:
alex bob
Affiliation:
acdm
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a stable release
Did you include all relevant data sets for reproducing the issue?
No - Other reason (please specify in the issue body)
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
The text was updated successfully, but these errors were encountered:
Thanks for raising this, if I understand this correctly this is about weird behaviour of https://shell.duckdb.org, it would be handy to move over as a duckdb/duckdb-wasm issue (@szarnyasg)
What happens?
When I trying to use DuckDB shell to add files with Chinese filenames and it's not working.
The webpage has crashed and is unresponsive.
But, DBeaver Client can normally read the same file without any issues.
Please Check.
To Reproduce
.files add
.files list
OS:
x86_64
DuckDB Version:
1.1.1
DuckDB Client:
shell
Hardware:
windows
Full Name:
alex bob
Affiliation:
acdm
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a stable release
Did you include all relevant data sets for reproducing the issue?
No - Other reason (please specify in the issue body)
Did you include all code required to reproduce the issue?
Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?
The text was updated successfully, but these errors were encountered: