pingcap/tidb

VALUES statement is not supported

Open

#21,486 opened on Dec 3, 2020

View on GitHub
 (13 comments) (0 reactions) (1 assignee)Go (6,186 forks)batch import
compatibility-mysql80help wantedsig/plannertype/compatibilitytype/new-feature

Repository metrics

Stars
 (40,090 stars)
PR merge metrics
 (Avg merge 14d 4h) (346 merged PRs in 30d)

Description

Description

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Execute the VALUES statement

values row(1);

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

mysql> values row(1);
+----------+
| column_0 |
+----------+
|        1 |
+----------+
1 row in set (0.00 sec)

3. What did you see instead (Required)

The query throws the 1051 Unknown Table error.

mysql> values row(1);
ERROR 1051 (42S02): Unknown table ''

4. What is your TiDB version? (Required)

e33b37789c616d7b7c997748cdd7eac6d6ec835c

Release Version: v8.1.0
Edition: Community
Git Commit Hash: 945d07c5d5c7a1ae212f6013adfb187f2de24b23
Git Branch: HEAD
UTC Build Time: 2024-05-21 03:52:40
GoVersion: go1.21.10
Race Enabled: false
Check Table Before Drop: false
Store: tikv

Contributor guide

Research direction
Examine how TiDB currently handles table less queries like 'SELECT 1' and trace the parsing and execution path to add support for the VALUES statement.
Tech stack
go
Domain
database
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60