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子查询,也不报错。

相关推荐
jiayou6414 分钟前
KingbaseES 实战:审计追踪配置与运维实践
数据库
NineData12 小时前
NineData 迁移评估功能正式上线
数据库·dba
NineData17 小时前
数据库迁移总踩坑?用 NineData 迁移评估,提前识别所有兼容性风险
数据库·程序员·云计算
赵渝强老师20 小时前
【赵渝强老师】PostgreSQL中表的碎片
数据库·postgresql
全栈老石1 天前
拆解低代码引擎核心:元数据驱动的"万能表"架构
数据库·低代码
倔强的石头_2 天前
kingbase备份与恢复实战(二)—— sys_dump库级逻辑备份与恢复(Windows详细步骤)
数据库
jiayou643 天前
KingbaseES 实战:深度解析数据库对象访问权限管理
数据库
李广坤4 天前
MySQL 大表字段变更实践(改名 + 改类型 + 改长度)
数据库
爱可生开源社区5 天前
2026 年,优秀的 DBA 需要具备哪些素质?
数据库·人工智能·dba
随逸1775 天前
《从零搭建NestJS项目》
数据库·typescript