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

相关推荐
wespaul6 小时前
VeapAI 自然语言操作实战|第 05 篇:向量与召回——从知识条目到可检索资产
大数据·数据库·人工智能·milvus
一只鹿鹿鹿11 小时前
政务外网整体设计方案(PPT)
大数据·数据库·web安全·系统安全·流程图·政务
2603_9651481111 小时前
社区与学习资源:从入门到精通的API选品学习路径
数据库·人工智能·python·学习·数据挖掘
AI砖家11 小时前
安全进入 Agent Loop:2027 年 Coding Agent 的决胜点
数据库·安全·codex·vibecoding
wangqiaowq12 小时前
SQL server C盘空间占满的处理
数据库·sql
文人sec12 小时前
SQL基础入门笔记 | 从零基础到掌握核心查询语句
数据库·笔记·sql
数字新视界12 小时前
机房动环监控提升运维效率
大数据·服务器·数据库·动环监控系统·动力与环境监控系统
SelectDB技术团队12 小时前
冷热分层从建到验:Storage Policy 创建、表级与分区级绑定、SHOW TABLETS 验证的完整命令
大数据·数据库·elasticsearch·搜索引擎·数据分析·apache doris·冷热分层
小玮看世界13 小时前
【Bug 报告】腾讯元宝 Windows 客户端 v2.88.1 新建对话卡死、界面残留与输入框乱码
bug
lambo mercy14 小时前
Day3:结构化输出
java·数据库·oracle