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
The following program triggers this internal error:
CREATE TABLE t21(c0 INT64);
CREATE TABLE t0(c0 INT64, c1 INT64);
CREATE VIEW v0(c0) AS SELECT t0.c1 FROM t21, t0;
WITH temp_table1 AS(SELECT (t21.c0) AS c0 FROM t21) SELECT (t0.rowid) AS c0 FROM v0, t0, temp_table1 WHERE ((temp_table1.c0)<(( t0.rowid)));
I notice there are two issues also related to this #5880 and #5039, I read your discussion and found the core of these two report is the type cast. But in this report, I use the same type INT64 and do not use any type cast. So I report this issue.
For this query, although temp_table1 is just an alias of t21, but its equivalent query SELECT (t0.rowid) AS c0 FROM v0, t0, t21 WHERE ((t21.c0)<(( t0.rowid))); can not trigger this internal error.
To Reproduce
I build duckdb from the latest commit version 98590fa
Closing for now since the example given in the description passes with this PR #8468. @DerZc If you are still experiencing a similar bug, feel free to file a new issue
What happens?
The following program triggers this internal error:
I notice there are two issues also related to this #5880 and #5039, I read your discussion and found the core of these two report is the type cast. But in this report, I use the same type
INT64
and do not use any type cast. So I report this issue.For this query, although
temp_table1
is just an alias oft21
, but its equivalent querySELECT (t0.rowid) AS c0 FROM v0, t0, t21 WHERE ((t21.c0)<(( t0.rowid)));
can not trigger this internal error.To Reproduce
I build duckdb from the latest commit version 98590fa
OS:
ubuntu 22.04
DuckDB Version:
98590fa
DuckDB Client:
CLI
Full Name:
Chi Zhang
Affiliation:
Nanjing University, National University of Singapore
Have you tried this on the latest
master
branch?Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
The text was updated successfully, but these errors were encountered: