We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
create table t(a numeric); insert into t values (1.8000), (1.346); select round(a, 2) from t;
With PG execution this returns:
round ─────── 1.80 1.35
With DuckDB execution this returns:
round ─────── 1.8 1.35
So we somehow lose the trailing 0 after rounding to two decimals. This causes differences in TPCDS output.
The text was updated successfully, but these errors were encountered:
FYI it seems that's because NUMERIC without a size is downgraded to a double in duckdb. I'm wondering if that's what we actually want to do.
NUMERIC
Sorry, something went wrong.
No branches or pull requests
Description
With PG execution this returns:
With DuckDB execution this returns:
So we somehow lose the trailing 0 after rounding to two decimals. This causes differences in TPCDS output.
The text was updated successfully, but these errors were encountered: