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
Interestingly, the results are different for different precision numeric types
duckdb=# create table numeric_test2(empno numeric(4,0), sal numeric(7,2) );
CREATE TABLE
duckdb=# insert into numeric_test2 select empno,sal from hi_emp_temp limit 1;
INSERT 01
duckdb=# select * from numeric_test2;
empno | sal
-------+--------7369 | 800.00
(1 row)
duckdb=# select count(*) from numeric_test2 where empno >= 0.25;
count
-------1
(1 row)
duckdb=# select count(*) from numeric_test2 where sal >= 0.25;2024-10-2323:36:13.095 CST [32922] ERROR: XX000: (PGDuckDB/ExecuteQuery) Invalid type Error: (DuckDB/FilterOperationSwitch) Unsupported duckdb type: 17002024-10-2323:36:13.095 CST [32922] LOCATION: DuckDBFunctionGuard, pgduckdb_utils.hpp:992024-10-2323:36:13.095 CST [32922] STATEMENT: selectcount(*) from numeric_test2 where sal >=0.25;
ERROR: (PGDuckDB/ExecuteQuery) Invalid type Error: (DuckDB/FilterOperationSwitch) Unsupported duckdb type: 1700
To Reproduce
createtablenumeric_test2(empno numeric(4,0), sal numeric(7,2));
insert into numeric_test2 values(7369,800.00);
select*from numeric_test2;
selectcount(*) from numeric_test2 where empno >=0.25;
selectcount(*) from numeric_test2 where sal >=0.25; -- error
What happens?
The numeric type is not supported as a where clause
To Reproduce
OS:
centos8
pg_duckdb Version:
master
Postgres Version:
REL_16_STABLE
Hardware:
No response
Full Name:
Man Zeng
Affiliation:
Halo
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a source build
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, Linux distribution) to reproduce the issue?
The text was updated successfully, but these errors were encountered: