pingcap / pingcap/tidb

Received an `Unknown column` error when using recursive CTE

Open
#45,181 1 comment 0 reactions 1 assignee Claimed by @elsa0520 View on GitHub
affects-7.5 affects-8.1 affects-8.5 may-affects-5.2 may-affects-5.3 may-affects-5.4 may-affects-6.1 may-affects-6.5 may-affects-7.1 severity/major sig/planner type/bug
Dominant language
Go
Stars
40.5k
Forks
6.2k
PR merge metrics
PR metrics pending

Description

## Bug Report

Please answer these questions before submitting your issue. Thanks!

### 1. Minimal reproduce step (Required)

```
CREATE TABLE some_table (
id INTEGER NOT NULL AUTO_INCREMENT,
data VARCHAR(50),
parent_id INTEGER,
PRIMARY KEY (id),
FOREIGN KEY(parent_id) REFERENCES some_table (id)
)

INSERT INTO some_table (id, data, parent_id) VALUES (1, 'd1', NULL),(2, 'd2', 1),(3, 'd3', 1),(4, 'd4', 3),(5, 'd5', 3)

WITH recursive some_cte(id, data, parent_id)
AS
(
SELECT some_table.id AS id,
some_table.data AS data,
some_table.parent_id AS parent_id
FROM some_table
WHERE some_table.data IN ('d2',
'd3',
'd4')
UNION ALL
SELECT some_table_1.id AS id,
some_table_1.data AS data,
some_table_1.parent_id AS parent_id
FROM some_table AS some_table_1,
some_cte AS c1
WHERE some_table_1.id = c1.parent_id
)
SELECT some_cte.data
FROM some_cte
WHERE some_cte.data != 'd2'
ORDER BY some_cte.data DESC
```

### 2. What did you expect to see? (Required)

```
+------+
| data |
+------+
| d4 |
| d3 |
| d3 |
| d1 |
| d1 |
| d1 |
+------+
```

### 3. What did you see instead (Required)

```
ERROR 1054 (42S22): Unknown column 'some_cte.data' in 'order clause'
```

### 4. What is your TiDB version? (Required)

Release Version: v7.2.0
Edition: Community
Git Commit Hash: 9fd5f4a8e4f273a60fbe7d3848f85a1be8f0600b
Git Branch: heads/refs/tags/v7.2.0
UTC Build Time: 2023-06-27 14:56:57
GoVersion: go1.20.5
Race Enabled: false
Check Table Before Drop: false
Store: tikv

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.