New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CURRENT_TIMESTAMP + INTERVAL 1 DAY fails #11949
Comments
Ah you probably need to load the ICU extension. It works from the command line (which loads ICU and parquet by default): (.venv) hawkfish@Richards-MacBook-Pro-5 duckdb % duckdb
v0.10.2 1601d94f94
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
D SELECT CURRENT_TIMESTAMP + INTERVAL 1 DAY;
┌──────────────────────────────────────────────────────────────────────────┐
│ (CURRENT_TIMESTAMP + to_days(CAST(trunc(CAST(1 AS DOUBLE)) AS INTEGER))) │
│ timestamp with time zone │
├──────────────────────────────────────────────────────────────────────────┤
│ 2024-05-06 11:54:28.147-07 │
└──────────────────────────────────────────────────────────────────────────┘ |
Interesting, that does appear to fix it. @carlopi is there any reason not to include this by default in duckdb-wasm? |
Thanks, this is an auto-loading issue with the LOAD icu;
SELECT CURRENT_TIMESTAMP + INTERVAL 1 DAY; |
Hi! This problem is connected to a limitation of autoloading when dealing with functions overloads. duckdb-wasm do not bundle the ICU extension (and there is a chance that even the CLI or other clients will eventually stop bundling it by default). |
Got it. We are just doing |
What happens?
In DuckDB wasm, which maps to
(this maps to duckdb-wasm
1.28.1-dev190.0
. I've also tested1.28.1-dev181.0
, which fails the same way).returns
This does not repro with the DuckDB cli, however.
To Reproduce
See repro above
OS:
mac os x
DuckDB Version:
library_version : "v0.10.2" source_id : "1601d94f94"
DuckDB Client:
wasm
Full Name:
Ankur Goyal
Affiliation:
Braintrust Data Inc
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?
Yes
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: