duckdb数据库CROSS JOIN LATERAL 中使用 EXISTS子查询的一个bug

以下代码片段改编自能够在PostgreSQL中正常执行的SQL。只把pi部分的/改写成了//。

sql 复制代码
WITH RECURSIVE
d(d) AS MATERIALIZED(SELECT d from generate_series(1, 9)t(d)),
pi(pos, r, c, bx) AS MATERIALIZED(
    SELECT 
        pos,
        ((pos - 1) // 9) + 1 AS r,
        ((pos - 1) % 9) + 1 AS c,
        ((pos - 1) // 9) // 3 * 3 + ((pos - 1) % 9) // 3 + 1 AS bx
    FROM generate_series(1, 81) AS t(pos)
),
cp(id, pz, bs) AS (
    SELECT 
        id,
        puzzle,
        regexp_split_to_array(
            regexp_replace(regexp_replace(puzzle, '[\r\n\s]', '', 'g'), '\?', '0', 'g'), 
            ''
        )::integer[] AS bs
FROM (SELECT 3 AS id, E'800000000003600000070090200050007000000045700000100030001000068008500010090000400' AS puzzle)sudoku9_9
),
s1(id,flag, bs,bse,i ) AS MATERIALIZED(
    SELECT id,'0', bs,ARRAY[]::integer[][], 0 AS i  FROM cp
    UNION ALL

    SELECT s1.id,n.flag, n.bs,n.bse, s1.i + 1 AS i
    FROM s1 s1
    CROSS JOIN LATERAL (
   	with
     eb(pos, r, c, bx, v) AS (SELECT pi.pos, pi.r, pi.c, pi.bx,1 FROM pi)
     ,
     cd(pos, r, c, bx, d) AS (
     SELECT e.pos, e.r, e.c, e.bx, d.d
            FROM eb e CROSS JOIN d 
            WHERE e.v = 0
              AND NOT EXISTS (SELECT 1 FROM eb e2 WHERE e2.r = e.r AND e2.v = d.d)
              AND NOT EXISTS (SELECT 1 FROM eb e2 WHERE e2.c = e.c AND e2.v = d.d)
              AND NOT EXISTS (SELECT 1 FROM eb e2 WHERE e2.bx = e.bx AND e2.v = d.d)
      )
     /* ,
     cd(pos, r, c, bx, d) AS (
      SELECT e.pos, e.r, e.c, e.bx, d.d
		FROM eb e 
		CROSS JOIN d
		LEFT JOIN eb e2 ON e2.r = e.r AND e2.v = d.d
		LEFT JOIN eb e3 ON e3.c = e.c AND e3.v = d.d
		LEFT JOIN eb e4 ON e4.bx = e.bx AND e4.v = d.d
		WHERE e.v = 0
		  AND e2.r IS NULL
		  AND e3.r IS NULL 
		  AND e4.r IS NULL 
    )*/
    SELECT '1' flag,bs, s1.bse from eb limit 1
   )n
   where s1.i < 3
)
select * from s1
;

执行报错

复制代码
Invalid Error:
vector::_M_range_check: __n (which is 2) >= this->size() (which is 2)

即使只有一个NOT EXISTS 语句,也会报同样错误。

将cd子查询改成注释块中的写法则能执行成功。

如果cd和eb不在JOIN LATERAL中,而是单独的CTE子查询,也不报错。

相关推荐
Database_Cool_8 分钟前
AnalyticDB MySQL vs Apache Doris:企业级云数仓如何选型——全维度对比指南
数据库·数据仓库·mysql·阿里云
心翼叶少9 分钟前
Redis(二):设置密码
数据库·redis·缓存
_Kafka_13 分钟前
Oracle平均成本计算流程
数据库·oracle
xfhuangfu13 分钟前
Oracle 19c中业务表的列发生变化时使用impdp
数据库·oracle
小何code37 分钟前
【Python零基础入门】第10篇:Python列表方法与应用实例
数据库·人工智能·python
Flash.kkl1 小时前
C++基于websocketpp的多用户网页五子棋项目
开发语言·网络·数据库·c++·websocket·mysql
kong@react1 小时前
milvus(向量数据库)docker容器(升级1.0)
数据库·docker·milvus
流烟默1 小时前
国产数据库CERDB 数据库实战:核心概念与备份恢复全攻略
数据库·数据库备份·cerdb
计算机安禾1 小时前
【算法分析与设计】第44篇:随机化复杂度类:RP、BPP与去随机化猜想
java·数据结构·数据库·算法·机器学习
Leon-Ning Liu1 小时前
Oracle恢复DELETE数据的PACKAGE(介绍篇)(仅做研究使用)
数据库·oracle