karths/binary_classification_train_comp
0147
1Unnamed: 0,id,type,created_at,repo,repo_url,action,title,labels,body,index,text_combine,label,text,binary_label28678,10605803336.0,IssuesEvent,2019-10-10 21:21:08,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,closed,SQL_BIG_RESULT syntax support.,type/compatibility,"Please answer these questions before submitting your issue. Thanks!
3
41. What did you do?
5
6```
7CREATE TABLE t1 (
8 spID int(10) unsigned,
9 userID int(10) unsigned,
10 score smallint(5) unsigned,
11 key (spid),
12 key (score)
13);
14
15select sql_big_result spid,sum(userid) from t1 group by spid;
16```
17
18
192. What did you expect to see?
20
21```
22mysql> select sql_big_result spid,sum(userid) from t1 group by spid;
23Empty set (0.00 sec)
24```
25
263. What did you see instead?
27
28```
29mysql> select sql_big_result spid,sum(userid) from t1 group by spid;
30ERROR 1054 (42S22): Unknown column 'sql_big_result' in 'field list'
31mysql> select spid,sum(userid) from t1 group by spid;
32Empty set (0.01 sec)
33```
34
35
364. What version of TiDB are you using (`tidb-server -V`)?
37
38```
39Release Version: 0.9.0
40Git Commit Hash: a7aaa64c76b5a1e5bb66caf94b888515cc334cf1
41Git Branch: master
42UTC Build Time: 2017-10-10 08:44:43
43```
44",True,"SQL_BIG_RESULT syntax support. - Please answer these questions before submitting your issue. Thanks!
45
461. What did you do?
47
48```
49CREATE TABLE t1 (
50 spID int(10) unsigned,
51 userID int(10) unsigned,
52 score smallint(5) unsigned,
53 key (spid),
54 key (score)
55);
56
57select sql_big_result spid,sum(userid) from t1 group by spid;
58```
59
60
612. What did you expect to see?
62
63```
64mysql> select sql_big_result spid,sum(userid) from t1 group by spid;
65Empty set (0.00 sec)
66```
67
683. What did you see instead?
69
70```
71mysql> select sql_big_result spid,sum(userid) from t1 group by spid;
72ERROR 1054 (42S22): Unknown column 'sql_big_result' in 'field list'
73mysql> select spid,sum(userid) from t1 group by spid;
74Empty set (0.01 sec)
75```
76
77
784. What version of TiDB are you using (`tidb-server -V`)?
79
80```
81Release Version: 0.9.0
82Git Commit Hash: a7aaa64c76b5a1e5bb66caf94b888515cc334cf1
83Git Branch: master
84UTC Build Time: 2017-10-10 08:44:43
85```
86",1,sql big result syntax support please answer these questions before submitting your issue thanks what did you do create table spid int unsigned userid int unsigned score smallint unsigned key spid key score select sql big result spid sum userid from group by spid what did you expect to see mysql select sql big result spid sum userid from group by spid empty set sec what did you see instead mysql select sql big result spid sum userid from group by spid error unknown column sql big result in field list mysql select spid sum userid from group by spid empty set sec what version of tidb are you using tidb server v release version git commit hash git branch master utc build time ,1877853,10062951627.0,IssuesEvent,2019-07-23 03:29:31,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,closed,alter database syntax support.,type/compatibility,"TiDB:
88
89```
90mysql> alter database test1 character set utf8 COLLATE uft8_general_ci;
91ERROR 1105 (HY000): line 0 column 14 near "" test1 character set utf8 COLLATE uft8_general_ci"" (total length 63)
92mysql> alter database test1 character set utf8 COLLATE uft8_general_ci;
93ERROR 1105 (HY000): line 0 column 14 near "" test1 character set utf8 COLLATE uft8_general_ci"" (total length 63)
94```
95
96see https://dev.mysql.com/doc/refman/5.7/en/alter-database.html",True,"alter database syntax support. - TiDB:
97
98```
99mysql> alter database test1 character set utf8 COLLATE uft8_general_ci;
100ERROR 1105 (HY000): line 0 column 14 near "" test1 character set utf8 COLLATE uft8_general_ci"" (total length 63)
101mysql> alter database test1 character set utf8 COLLATE uft8_general_ci;
102ERROR 1105 (HY000): line 0 column 14 near "" test1 character set utf8 COLLATE uft8_general_ci"" (total length 63)
103```
104
105see https://dev.mysql.com/doc/refman/5.7/en/alter-database.html",1,alter database syntax support tidb mysql alter database character set collate general ci error line column near character set collate general ci total length mysql alter database character set collate general ci error line column near character set collate general ci total length see ,11068998,11034837643.0,IssuesEvent,2019-12-07 09:01:45,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,opened,Datetime compare incompatible with MySQL,type/bug type/compatibility,"## Bug Report
107
108Please answer these questions before submitting your issue. Thanks!
109
1101. What did you do?
111
112```
113CREATE TABLE t(d datetime);
114INSERT INTO t(d) VALUES('2019-08-10 11:45:14');
115SELECT d, d > 1 FROM t;
116SELECT COUNT(1) FROM t WHERE d > 1;
117```
118
119
1202. What did you expect to see?
121
122* MySQL 8.0
123
124```
125mysql> CREATE TABLE t(d datetime);
126Query OK, 0 rows affected (0.01 sec)
127
128mysql> INSERT INTO t(d) VALUES('2019-08-10 11:45:14');
129Query OK, 1 row affected (0.00 sec)
130
131mysql> SELECT d, d > 1 FROM t;
132+---------------------+-------+
133| d | d > 1 |
134+---------------------+-------+
135| 2019-08-10 11:45:14 | 1 |
136+---------------------+-------+
1371 row in set, 1 warning (0.02 sec)
138
139mysql> SELECT COUNT(1) FROM t WHERE d > 1;
140+----------+
141| COUNT(1) |
142+----------+
143| 1 |
144+----------+
1451 row in set, 1 warning (0.04 sec)
146
147mysql> SELECT version();
148+-----------+
149| version() |
150+-----------+
151| 8.0.18 |
152+-----------+
1531 row in set (0.00 sec)
154```
155
156
1573. What did you see instead?
158
159* TiDB 3.0.7
160
161```
162mysql> CREATE TABLE t(d datetime);
163Query OK, 0 rows affected (1.01 sec)
164
165mysql> INSERT INTO t(d) VALUES('2019-08-10 11:45:14');
166Query OK, 1 row affected (0.01 sec)
167
168mysql> SELECT d, d > 1 FROM t;
169+---------------------+-------+
170| d | d > 1 |
171+---------------------+-------+
172| 2019-08-10 11:45:14 | NULL |
173+---------------------+-------+
1741 row in set, 1 warning (0.01 sec)
175
176mysql> SELECT COUNT(1) FROM t WHERE d > 1;
177+----------+
178| COUNT(1) |
179+----------+
180| 0 |
181+----------+
1821 row in set, 1 warning (0.00 sec)
183
184mysql> SELECT version();
185+--------------------+
186| version() |
187+--------------------+
188| 5.7.25-TiDB-v3.0.7 |
189+--------------------+
1901 row in set (0.00 sec)
191```
192
1934. What version of TiDB are you using (`tidb-server -V` or run `select tidb_version();` on TiDB)?
194
195```
196Release Version: v3.0.7
197Git Commit Hash: 84e4386c7a77d4b8df5db7f2303fb7fd3370eb9a
198Git Branch: HEAD
199UTC Build Time: 2019-12-04 10:08:24
200GoVersion: go version go1.13 linux/amd64
201Race Enabled: false
202TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
203Check Table Before Drop: false
204```
205",True,"Datetime compare incompatible with MySQL - ## Bug Report
206
207Please answer these questions before submitting your issue. Thanks!
208
2091. What did you do?
210
211```
212CREATE TABLE t(d datetime);
213INSERT INTO t(d) VALUES('2019-08-10 11:45:14');
214SELECT d, d > 1 FROM t;
215SELECT COUNT(1) FROM t WHERE d > 1;
216```
217
218
2192. What did you expect to see?
220
221* MySQL 8.0
222
223```
224mysql> CREATE TABLE t(d datetime);
225Query OK, 0 rows affected (0.01 sec)
226
227mysql> INSERT INTO t(d) VALUES('2019-08-10 11:45:14');
228Query OK, 1 row affected (0.00 sec)
229
230mysql> SELECT d, d > 1 FROM t;
231+---------------------+-------+
232| d | d > 1 |
233+---------------------+-------+
234| 2019-08-10 11:45:14 | 1 |
235+---------------------+-------+
2361 row in set, 1 warning (0.02 sec)
237
238mysql> SELECT COUNT(1) FROM t WHERE d > 1;
239+----------+
240| COUNT(1) |
241+----------+
242| 1 |
243+----------+
2441 row in set, 1 warning (0.04 sec)
245
246mysql> SELECT version();
247+-----------+
248| version() |
249+-----------+
250| 8.0.18 |
251+-----------+
2521 row in set (0.00 sec)
253```
254
255
2563. What did you see instead?
257
258* TiDB 3.0.7
259
260```
261mysql> CREATE TABLE t(d datetime);
262Query OK, 0 rows affected (1.01 sec)
263
264mysql> INSERT INTO t(d) VALUES('2019-08-10 11:45:14');
265Query OK, 1 row affected (0.01 sec)
266
267mysql> SELECT d, d > 1 FROM t;
268+---------------------+-------+
269| d | d > 1 |
270+---------------------+-------+
271| 2019-08-10 11:45:14 | NULL |
272+---------------------+-------+
2731 row in set, 1 warning (0.01 sec)
274
275mysql> SELECT COUNT(1) FROM t WHERE d > 1;
276+----------+
277| COUNT(1) |
278+----------+
279| 0 |
280+----------+
2811 row in set, 1 warning (0.00 sec)
282
283mysql> SELECT version();
284+--------------------+
285| version() |
286+--------------------+
287| 5.7.25-TiDB-v3.0.7 |
288+--------------------+
2891 row in set (0.00 sec)
290```
291
2924. What version of TiDB are you using (`tidb-server -V` or run `select tidb_version();` on TiDB)?
293
294```
295Release Version: v3.0.7
296Git Commit Hash: 84e4386c7a77d4b8df5db7f2303fb7fd3370eb9a
297Git Branch: HEAD
298UTC Build Time: 2019-12-04 10:08:24
299GoVersion: go version go1.13 linux/amd64
300Race Enabled: false
301TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
302Check Table Before Drop: false
303```
304",1,datetime compare incompatible with mysql bug report please answer these questions before submitting your issue thanks what did you do create table t d datetime insert into t d values select d d from t select count from t where d what did you expect to see mysql mysql create table t d datetime query ok rows affected sec mysql insert into t d values query ok row affected sec mysql select d d from t d d row in set warning sec mysql select count from t where d count row in set warning sec mysql select version version row in set sec what did you see instead tidb mysql create table t d datetime query ok rows affected sec mysql insert into t d values query ok row affected sec mysql select d d from t d d null row in set warning sec mysql select count from t where d count row in set warning sec mysql select version version tidb row in set sec what version of tidb are you using tidb server v or run select tidb version on tidb release version git commit hash git branch head utc build time goversion go version linux race enabled false tikv min version check table before drop false ,13057334,9577312403.0,IssuesEvent,2019-05-07 11:21:08,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,closed,`unix_timestamp` is not compatible with Mysql,for new contributors help wanted type/bug type/compatibility,"## Bug Report
306
307Please answer these questions before submitting your issue. Thanks!
308
3091. What did you do?
310If possible, provide a recipe for reproducing the error.
311```
312select @a:=FROM_UNIXTIME(1);
313select unix_timestamp(@a);
314```
315
3162. What did you expect to see?
317In Mysql
318```
319mysql> select @a:=FROM_UNIXTIME(1);
320+----------------------+
321| @a:=FROM_UNIXTIME(1) |
322+----------------------+
323| 1970-01-01 08:00:01 |
324+----------------------+
3251 row in set (0.00 sec)
326
327mysql> select unix_timestamp(@a);
328+--------------------+
329| unix_timestamp(@a) |
330+--------------------+
331| 1 |
332+--------------------+
3331 row in set (0.00 sec)
334```
335
336
3373. What did you see instead?
338In TiDB
339```
340mysql> select @a:=FROM_UNIXTIME(1);
341+----------------------+
342| @a:=FROM_UNIXTIME(1) |
343+----------------------+
344| 1970-01-01 08:00:01 |
345+----------------------+
3461 row in set (0.00 sec)
347
348mysql> select unix_timestamp(@a);
349+--------------------+
350| unix_timestamp(@a) |
351+--------------------+
352| 1.000000 |
353+--------------------+
3541 row in set (0.01 sec)
355```
356
357
3584. What version of TiDB are you using (`tidb-server -V` or run `select tidb_version();` on TiDB)?
359```
360+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
361| tidb_version() |
362+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
363| Release Version: v3.0.0-beta-212-g0681b8125
364Git Commit Hash: 0681b8125080045ee0d4747ce61923164c6f2dd1
365Git Branch: master
366UTC Build Time: 2019-03-14 04:39:19
367GoVersion: go version go1.12 darwin/amd64
368Race Enabled: false
369TiKV Min Version: 2.1.0-alpha.1-ff3dd160846b7d1aed9079c389fc188f7f5ea13e
370Check Table Before Drop: false |
371+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
372```
373
374",True,"`unix_timestamp` is not compatible with Mysql - ## Bug Report
375
376Please answer these questions before submitting your issue. Thanks!
377
3781. What did you do?
379If possible, provide a recipe for reproducing the error.
380```
381select @a:=FROM_UNIXTIME(1);
382select unix_timestamp(@a);
383```
384
3852. What did you expect to see?
386In Mysql
387```
388mysql> select @a:=FROM_UNIXTIME(1);
389+----------------------+
390| @a:=FROM_UNIXTIME(1) |
391+----------------------+
392| 1970-01-01 08:00:01 |
393+----------------------+
3941 row in set (0.00 sec)
395
396mysql> select unix_timestamp(@a);
397+--------------------+
398| unix_timestamp(@a) |
399+--------------------+
400| 1 |
401+--------------------+
4021 row in set (0.00 sec)
403```
404
405
4063. What did you see instead?
407In TiDB
408```
409mysql> select @a:=FROM_UNIXTIME(1);
410+----------------------+
411| @a:=FROM_UNIXTIME(1) |
412+----------------------+
413| 1970-01-01 08:00:01 |
414+----------------------+
4151 row in set (0.00 sec)
416
417mysql> select unix_timestamp(@a);
418+--------------------+
419| unix_timestamp(@a) |
420+--------------------+
421| 1.000000 |
422+--------------------+
4231 row in set (0.01 sec)
424```
425
426
4274. What version of TiDB are you using (`tidb-server -V` or run `select tidb_version();` on TiDB)?
428```
429+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
430| tidb_version() |
431+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
432| Release Version: v3.0.0-beta-212-g0681b8125
433Git Commit Hash: 0681b8125080045ee0d4747ce61923164c6f2dd1
434Git Branch: master
435UTC Build Time: 2019-03-14 04:39:19
436GoVersion: go version go1.12 darwin/amd64
437Race Enabled: false
438TiKV Min Version: 2.1.0-alpha.1-ff3dd160846b7d1aed9079c389fc188f7f5ea13e
439Check Table Before Drop: false |
440+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
441```
442
443",1, unix timestamp is not compatible with mysql bug report please answer these questions before submitting your issue thanks what did you do if possible provide a recipe for reproducing the error select a from unixtime select unix timestamp a what did you expect to see in mysql mysql select a from unixtime a from unixtime row in set sec mysql select unix timestamp a unix timestamp a row in set sec what did you see instead in tidb mysql select a from unixtime a from unixtime row in set sec mysql select unix timestamp a unix timestamp a row in set sec what version of tidb are you using tidb server v or run select tidb version on tidb tidb version release version beta git commit hash git branch master utc build time goversion go version darwin race enabled false tikv min version alpha check table before drop false ,144411861,13995564192.0,IssuesEvent,2020-10-28 03:36:04,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,closed,Support multiple table rename (swap table use case),challenge-program difficulty/medium high-performance picked sig/DDL type/compatibility type/enhancement,"## Feature Request
445
446**Is your feature request related to a problem? Please describe:**
447
448I know that multiple DDL changes are currently on the roadmap. My feature request is to support a much smaller subset, which is an atomic rename of two tables.
449
450This supports the use case of swapping tables, something that occurs frequently in the replication stream due to its usage by tools such as `pt-online-schema-change`.
451
452**Describe the feature you'd like:**
453
454```
455mysql> CREATE TABLE t1 (a int);
456Query OK, 0 rows affected (0.01 sec)
457
458mysql> CREATE TABLE t2 (a int, b int);
459Query OK, 0 rows affected (0.01 sec)
460
461mysql> RENAME TABLE t1 to t1_old, t2 to t1; <--- should work
462ERROR 1105 (HY000): can't run multi schema change
463```
464
465**Describe alternatives you've considered:**
466
467The alternative is to do this non-atomically (breaks apps) or under a global lock (not yet supported by TiDB). So there is not really a good alternative.
468
469**Teachability, Documentation, Adoption, Migration Strategy:**
470
471MySQL compatible behavior.
472
473## Score
4741500
475
476## SIG Slack Channel
477You can join [#sig-ddl ](https://app.slack.com/client/TH91JCS4W/CMAKWBNJU)on slack in your spare time to discuss and get help with mentors or others.
478
479## Mentor(s)
480* @zimulala
481
482## Recommended Skills
483* DDL
484* Golang
485
486## Learning Materials
487MySQL's [document](https://dev.mysql.com/doc/refman/8.0/en/invisible-indexes.html) for syntax reference.
488[TiDB DDL architecture](https://github.com/pingcap/tidb/blob/master/docs/design/2018-10-08-online-DDL.md)",True,"Support multiple table rename (swap table use case) - ## Feature Request
489
490**Is your feature request related to a problem? Please describe:**
491
492I know that multiple DDL changes are currently on the roadmap. My feature request is to support a much smaller subset, which is an atomic rename of two tables.
493
494This supports the use case of swapping tables, something that occurs frequently in the replication stream due to its usage by tools such as `pt-online-schema-change`.
495
496**Describe the feature you'd like:**
497
498```
499mysql> CREATE TABLE t1 (a int);
500Query OK, 0 rows affected (0.01 sec)
501
502mysql> CREATE TABLE t2 (a int, b int);
503Query OK, 0 rows affected (0.01 sec)
504
505mysql> RENAME TABLE t1 to t1_old, t2 to t1; <--- should work
506ERROR 1105 (HY000): can't run multi schema change
507```
508
509**Describe alternatives you've considered:**
510
511The alternative is to do this non-atomically (breaks apps) or under a global lock (not yet supported by TiDB). So there is not really a good alternative.
512
513**Teachability, Documentation, Adoption, Migration Strategy:**
514
515MySQL compatible behavior.
516
517## Score
5181500
519
520## SIG Slack Channel
521You can join [#sig-ddl ](https://app.slack.com/client/TH91JCS4W/CMAKWBNJU)on slack in your spare time to discuss and get help with mentors or others.
522
523## Mentor(s)
524* @zimulala
525
526## Recommended Skills
527* DDL
528* Golang
529
530## Learning Materials
531MySQL's [document](https://dev.mysql.com/doc/refman/8.0/en/invisible-indexes.html) for syntax reference.
532[TiDB DDL architecture](https://github.com/pingcap/tidb/blob/master/docs/design/2018-10-08-online-DDL.md)",1,support multiple table rename swap table use case feature request is your feature request related to a problem please describe i know that multiple ddl changes are currently on the roadmap my feature request is to support a much smaller subset which is an atomic rename of two tables this supports the use case of swapping tables something that occurs frequently in the replication stream due to its usage by tools such as pt online schema change describe the feature you d like mysql create table a int query ok rows affected sec mysql create table a int b int query ok rows affected sec mysql rename table to old to should work error can t run multi schema change describe alternatives you ve considered the alternative is to do this non atomically breaks apps or under a global lock not yet supported by tidb so there is not really a good alternative teachability documentation adoption migration strategy mysql compatible behavior score sig slack channel you can join slack in your spare time to discuss and get help with mentors or others mentor s zimulala recommended skills ddl golang learning materials mysql s for syntax reference ,153320510,30333744748.0,IssuesEvent,2023-07-11 08:15:55,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,opened,Sleep in subquery not executed correctly,type/bug type/compatibility sig/sql-infra severity/minor compatibility-mysql8,"## Bug Report
534
535When calling `SLEEP()` multiple times in separate subqueries the execution time is not the expected execution time.
536
537### 1. Minimal reproduce step (Required)
538
539```
540SELECT SLEEP(2) UNION ALL SELECT SLEEP(3);
541SELECT SLEEP(2),SLEEP(3);
542```
543
544### 2. What did you expect to see? (Required)
545
546Both statements taking 5s each.
547
548### 3. What did you see instead (Required)
549
550```
551mysql> SELECT SLEEP(2) UNION ALL SELECT SLEEP(3);
552+----------+
553| SLEEP(2) |
554+----------+
555| 0 |
556| 0 |
557+----------+
5582 rows in set (3.00 sec)
559
560mysql> SELECT SLEEP(2),SLEEP(3);
561+----------+----------+
562| SLEEP(2) | SLEEP(3) |
563+----------+----------+
564| 0 | 0 |
565+----------+----------+
5661 row in set (5.00 sec)
567```
568
569### 4. What is your TiDB version? (Required)
570
571<!-- Paste the output of SELECT tidb_version() -->
572
573```
574Release Version: v7.3.0-alpha-160-g90dabc0433
575Edition: Community
576Git Commit Hash: 90dabc0433a75db650ac683897d264ef58d63a73
577Git Branch: master
578UTC Build Time: 2023-07-11 07:57:57
579GoVersion: go1.20.5
580Race Enabled: false
581Check Table Before Drop: false
582Store: unistore
583```",True,"Sleep in subquery not executed correctly - ## Bug Report
584
585When calling `SLEEP()` multiple times in separate subqueries the execution time is not the expected execution time.
586
587### 1. Minimal reproduce step (Required)
588
589```
590SELECT SLEEP(2) UNION ALL SELECT SLEEP(3);
591SELECT SLEEP(2),SLEEP(3);
592```
593
594### 2. What did you expect to see? (Required)
595
596Both statements taking 5s each.
597
598### 3. What did you see instead (Required)
599
600```
601mysql> SELECT SLEEP(2) UNION ALL SELECT SLEEP(3);
602+----------+
603| SLEEP(2) |
604+----------+
605| 0 |
606| 0 |
607+----------+
6082 rows in set (3.00 sec)
609
610mysql> SELECT SLEEP(2),SLEEP(3);
611+----------+----------+
612| SLEEP(2) | SLEEP(3) |
613+----------+----------+
614| 0 | 0 |
615+----------+----------+
6161 row in set (5.00 sec)
617```
618
619### 4. What is your TiDB version? (Required)
620
621<!-- Paste the output of SELECT tidb_version() -->
622
623```
624Release Version: v7.3.0-alpha-160-g90dabc0433
625Edition: Community
626Git Commit Hash: 90dabc0433a75db650ac683897d264ef58d63a73
627Git Branch: master
628UTC Build Time: 2023-07-11 07:57:57
629GoVersion: go1.20.5
630Race Enabled: false
631Check Table Before Drop: false
632Store: unistore
633```",1,sleep in subquery not executed correctly bug report when calling sleep multiple times in separate subqueries the execution time is not the expected execution time minimal reproduce step required select sleep union all select sleep select sleep sleep what did you expect to see required both statements taking each what did you see instead required mysql select sleep union all select sleep sleep rows in set sec mysql select sleep sleep sleep sleep row in set sec what is your tidb version required release version alpha edition community git commit hash git branch master utc build time goversion race enabled false check table before drop false store unistore ,163413155,15496099739.0,IssuesEvent,2021-03-11 02:03:37,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,reopened,Test compatibility using DataGrip,status/help-wanted type/compatibility,"DataGrip is a Database management systems that support many databases, including MySQL. See https://www.jetbrains.com/datagrip/
635",True,"Test compatibility using DataGrip - DataGrip is a Database management systems that support many databases, including MySQL. See https://www.jetbrains.com/datagrip/
636",1,test compatibility using datagrip datagrip is a database management systems that support many databases including mysql see ,16373400,6366812778.0,IssuesEvent,2017-08-01 03:10:22,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,opened,str_to_date function is not compatible with MySQL,compatibility rc3.1,"Please answer these questions before submitting your issue. Thanks!
638
6391. What did you do?
640If possible, provide a recipe for reproducing the error.
641
642```sql
643select str_to_date('04 /30/2004', '%m /%d/%Y');
644```
645
6462. What did you expect to see?
647
6482004-04-30
649
6503. What did you see instead?
651
6522004-04-30 00:00:00
653
6544. What version of TiDB are you using (`tidb-server -V`)?
655
656",True,"str_to_date function is not compatible with MySQL - Please answer these questions before submitting your issue. Thanks!
657
6581. What did you do?
659If possible, provide a recipe for reproducing the error.
660
661```sql
662select str_to_date('04 /30/2004', '%m /%d/%Y');
663```
664
6652. What did you expect to see?
666
6672004-04-30
668
6693. What did you see instead?
670
6712004-04-30 00:00:00
672
6734. What version of TiDB are you using (`tidb-server -V`)?
674
675",1,str to date function is not compatible with mysql please answer these questions before submitting your issue thanks what did you do if possible provide a recipe for reproducing the error sql select str to date m d y what did you expect to see what did you see instead what version of tidb are you using tidb server v ,167612178,14354611704.0,IssuesEvent,2020-11-30 08:55:52,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,closed,Support LIST COLUMNS partitioning,feature/accepted status/help-wanted type/compatibility type/feature-request,"## Feature Request
677
678**Is your feature request related to a problem? Please describe:**
679<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
680
681MySQL support [LIST COLUMNS](https://dev.mysql.com/doc/refman/8.0/en/partitioning-columns-list.html) partition but TiDB didn't support it now.
682
683support it will help mysql user migrate to TiDB
684
685**Describe the feature you'd like:**
686<!-- A clear and concise description of what you want to happen. -->
687
688Compatible with MySQL's [LIST COLUMNS](https://dev.mysql.com/doc/refman/8.0/en/partitioning-columns-list.html) partition
689
690**Describe alternatives you've considered:**
691<!-- A clear and concise description of any alternative solutions or features you've considered. -->
692
693n/a
694
695**Teachability, Documentation, Adoption, Migration Strategy:**
696<!-- If you can, explain some scenarios how users might use this, situations it would be helpful in. Any API designs, mockups, or diagrams are also helpful. -->
697",True,"Support LIST COLUMNS partitioning - ## Feature Request
698
699**Is your feature request related to a problem? Please describe:**
700<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
701
702MySQL support [LIST COLUMNS](https://dev.mysql.com/doc/refman/8.0/en/partitioning-columns-list.html) partition but TiDB didn't support it now.
703
704support it will help mysql user migrate to TiDB
705
706**Describe the feature you'd like:**
707<!-- A clear and concise description of what you want to happen. -->
708
709Compatible with MySQL's [LIST COLUMNS](https://dev.mysql.com/doc/refman/8.0/en/partitioning-columns-list.html) partition
710
711**Describe alternatives you've considered:**
712<!-- A clear and concise description of any alternative solutions or features you've considered. -->
713
714n/a
715
716**Teachability, Documentation, Adoption, Migration Strategy:**
717<!-- If you can, explain some scenarios how users might use this, situations it would be helpful in. Any API designs, mockups, or diagrams are also helpful. -->
718",1,support list columns partitioning feature request is your feature request related to a problem please describe mysql support partition but tidb didn t support it now support it will help mysql user migrate to tidb describe the feature you d like compatible with mysql s partition describe alternatives you ve considered n a teachability documentation adoption migration strategy ,17195724,8183087581.0,IssuesEvent,2018-08-29 07:58:00,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,closed,SHOW GRANTS FOR CURRENT_USER() does not work,type/compatibility,"Hi.
720I'm execute command（by mysql cli）
721`SHOW GRANTS FOR CURRENT_USER();`
722
723get the error
724`
725ERROR 1105 (HY000): line 1 column 28 near ""()"" (total length 30)
726`
727
728tidb version:
729`5.7.1-TiDB-v1.1.0-alpha-459-ga2a48b3`
730
731
732BTW .
733tidb support MySQL Protocol , but not very compatible with MySQL's existing client tools ( `Navicat`， `MySQL-Front`，`mysql workbench` and so on ) . Less convenient for developers to use it.
734",True,"SHOW GRANTS FOR CURRENT_USER() does not work - Hi.
735I'm execute command（by mysql cli）
736`SHOW GRANTS FOR CURRENT_USER();`
737
738get the error
739`
740ERROR 1105 (HY000): line 1 column 28 near ""()"" (total length 30)
741`
742
743tidb version:
744`5.7.1-TiDB-v1.1.0-alpha-459-ga2a48b3`
745
746
747BTW .
748tidb support MySQL Protocol , but not very compatible with MySQL's existing client tools ( `Navicat`， `MySQL-Front`，`mysql workbench` and so on ) . Less convenient for developers to use it.
749",1,show grants for current user does not work hi i m execute command（by mysql cli） show grants for current user get the error error line column near total length tidb version tidb alpha btw tidb support mysql protocol but not very compatible with mysql s existing client tools navicat ， mysql front ， mysql workbench and so on less convenient for developers to use it ,175018246,25237672188.0,IssuesEvent,2022-11-15 03:13:58,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,closed,"`bit`, `char` type column metadata is not compatible with mysql.",type/bug type/compatibility sig/sql-infra severity/moderate,"## Bug Report
751
752Please answer these questions before submitting your issue. Thanks!
753
754### 1. Minimal reproduce step (Required)
755
756```
757CREATE TABLE `PK_MULTI_COL_527_tmp` (
758 `COL1` char(10) COLLATE utf8_general_ci NOT NULL,
759 `COL3` bit(1) NOT NULL,
760 PRIMARY KEY (`COL1`(5),`COL3`) /*T![clustered_index] NONCLUSTERED */
761) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci;
762
763select table_catalog table_catalog,table_name table_name,column_name column_name,ordinal_position ordinal_position,column_default column_default,is_nullable is_nullable,data_type data_type,character_maximum_length character_maximum_length,character_octet_length character_octet_length,numeric_precision numeric_precision,numeric_scale numeric_scale,datetime_precision datetime_precision,character_set_name character_set_name,collation_name collation_name,column_type column_type,column_key column_key,extra extra,privileges privileges,column_comment column_comment,generation_expression generation_expression from information_schema.columns where table_schema=(select database()) and table_name=""PK_MULTI_COL_527_tmp"" order by ordinal_position;
764
765
766```
767### 2. What did you expect to see? (Required)
768
769```
770+---------------+----------------------+-------------+------------------+----------------+-------------+-----------+--------------------------+------------------------+-------------------+---------------+--------------------+--------------------+-----------------+-----------------+------------+-------+---------------------------------+----------------+-----------------------+
771| table_catalog | table_name | column_name | ordinal_position | column_default | is_nullable | data_type | character_maximum_length | character_octet_length | numeric_precision | numeric_scale | datetime_precision | character_set_name | collation_name | column_type | column_key | extra | privileges | column_comment | generation_expression |
772+---------------+----------------------+-------------+------------------+----------------+-------------+-----------+--------------------------+------------------------+-------------------+---------------+--------------------+--------------------+-----------------+-----------------+------------+-------+---------------------------------+----------------+-----------------------+
773| def | PK_MULTI_COL_527_tmp | COL1 | 1 | NULL | NO | char | 10 | 30 | NULL | NULL | NULL | utf8 | utf8_general_ci | char(10) | PRI | | select,insert,update,references | | |
774| def | PK_MULTI_COL_527_tmp | COL3 | 2 | NULL | NO | bit | NULL | NULL | 1 | NULL | NULL | NULL | NULL | bit(1) | PRI | | select,insert,update,references | | |
775+---------------+----------------------+-------------+------------------+----------------+-------------+-----------+--------------------------+------------------------+-------------------+---------------+--------------------+--------------------+-----------------+-----------------+------------+-------+---------------------------------+----------------+-----------------------+
776```
777
778### 3. What did you see instead (Required)
779
780```
781+---------------+----------------------+-------------+------------------+----------------+-------------+-----------+--------------------------+------------------------+-------------------+---------------+--------------------+--------------------+-----------------+-----------------+------------+-------+---------------------------------+----------------+-----------------------+
782| table_catalog | table_name | column_name | ordinal_position | column_default | is_nullable | data_type | character_maximum_length | character_octet_length | numeric_precision | numeric_scale | datetime_precision | character_set_name | collation_name | column_type | column_key | extra | privileges | column_comment | generation_expression |
783+---------------+----------------------+-------------+------------------+----------------+-------------+-----------+--------------------------+------------------------+-------------------+---------------+--------------------+--------------------+-----------------+-----------------+------------+-------+---------------------------------+----------------+-----------------------+
784| def | PK_MULTI_COL_527_tmp | COL1 | 1 | NULL | NO | char | 10 | 10 | NULL | NULL | NULL | utf8 | utf8_general_ci | char(10) | PRI | | select,insert,update,references | | |
785| def | PK_MULTI_COL_527_tmp | COL3 | 2 | NULL | NO | bit | NULL | NULL | 1 | 0 | NULL | NULL | NULL | bit(1) unsigned | PRI | | select,insert,update,references | | |
786+---------------+----------------------+-------------+------------------+----------------+-------------+-----------+--------------------------+------------------------+-------------------+---------------+--------------------+--------------------+-----------------+-----------------+------------+-------+---------------------------------+----------------+-----------------------+
787```
788### 4. What is your TiDB version? (Required)
789
790```
791-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
792| tidb_version() |
793+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
794| Release Version: v5.1.0-20210611
795Edition: Community
796Git Commit Hash: 29bfbb28437609d0a524b7b84e6920dc765978c7
797Git Branch: heads/refs/tags/v5.1.0-20210611
798UTC Build Time: 2021-06-11 07:52:09
799GoVersion: go1.16.4
800Race Enabled: false
801TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
802Check Table Before Drop: false |
803+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
804
805```
806",True,"`bit`, `char` type column metadata is not compatible with mysql. - ## Bug Report
807
808Please answer these questions before submitting your issue. Thanks!
809
810### 1. Minimal reproduce step (Required)
811
812```
813CREATE TABLE `PK_MULTI_COL_527_tmp` (
814 `COL1` char(10) COLLATE utf8_general_ci NOT NULL,
815 `COL3` bit(1) NOT NULL,
816 PRIMARY KEY (`COL1`(5),`COL3`) /*T![clustered_index] NONCLUSTERED */
817) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci;
818
819select table_catalog table_catalog,table_name table_name,column_name column_name,ordinal_position ordinal_position,column_default column_default,is_nullable is_nullable,data_type data_type,character_maximum_length character_maximum_length,character_octet_length character_octet_length,numeric_precision numeric_precision,numeric_scale numeric_scale,datetime_precision datetime_precision,character_set_name character_set_name,collation_name collation_name,column_type column_type,column_key column_key,extra extra,privileges privileges,column_comment column_comment,generation_expression generation_expression from information_schema.columns where table_schema=(select database()) and table_name=""PK_MULTI_COL_527_tmp"" order by ordinal_position;
820
821
822```
823### 2. What did you expect to see? (Required)
824
825```
826+---------------+----------------------+-------------+------------------+----------------+-------------+-----------+--------------------------+------------------------+-------------------+---------------+--------------------+--------------------+-----------------+-----------------+------------+-------+---------------------------------+----------------+-----------------------+
827| table_catalog | table_name | column_name | ordinal_position | column_default | is_nullable | data_type | character_maximum_length | character_octet_length | numeric_precision | numeric_scale | datetime_precision | character_set_name | collation_name | column_type | column_key | extra | privileges | column_comment | generation_expression |
828+---------------+----------------------+-------------+------------------+----------------+-------------+-----------+--------------------------+------------------------+-------------------+---------------+--------------------+--------------------+-----------------+-----------------+------------+-------+---------------------------------+----------------+-----------------------+
829| def | PK_MULTI_COL_527_tmp | COL1 | 1 | NULL | NO | char | 10 | 30 | NULL | NULL | NULL | utf8 | utf8_general_ci | char(10) | PRI | | select,insert,update,references | | |
830| def | PK_MULTI_COL_527_tmp | COL3 | 2 | NULL | NO | bit | NULL | NULL | 1 | NULL | NULL | NULL | NULL | bit(1) | PRI | | select,insert,update,references | | |
831+---------------+----------------------+-------------+------------------+----------------+-------------+-----------+--------------------------+------------------------+-------------------+---------------+--------------------+--------------------+-----------------+-----------------+------------+-------+---------------------------------+----------------+-----------------------+
832```
833
834### 3. What did you see instead (Required)
835
836```
837+---------------+----------------------+-------------+------------------+----------------+-------------+-----------+--------------------------+------------------------+-------------------+---------------+--------------------+--------------------+-----------------+-----------------+------------+-------+---------------------------------+----------------+-----------------------+
838| table_catalog | table_name | column_name | ordinal_position | column_default | is_nullable | data_type | character_maximum_length | character_octet_length | numeric_precision | numeric_scale | datetime_precision | character_set_name | collation_name | column_type | column_key | extra | privileges | column_comment | generation_expression |
839+---------------+----------------------+-------------+------------------+----------------+-------------+-----------+--------------------------+------------------------+-------------------+---------------+--------------------+--------------------+-----------------+-----------------+------------+-------+---------------------------------+----------------+-----------------------+
840| def | PK_MULTI_COL_527_tmp | COL1 | 1 | NULL | NO | char | 10 | 10 | NULL | NULL | NULL | utf8 | utf8_general_ci | char(10) | PRI | | select,insert,update,references | | |
841| def | PK_MULTI_COL_527_tmp | COL3 | 2 | NULL | NO | bit | NULL | NULL | 1 | 0 | NULL | NULL | NULL | bit(1) unsigned | PRI | | select,insert,update,references | | |
842+---------------+----------------------+-------------+------------------+----------------+-------------+-----------+--------------------------+------------------------+-------------------+---------------+--------------------+--------------------+-----------------+-----------------+------------+-------+---------------------------------+----------------+-----------------------+
843```
844### 4. What is your TiDB version? (Required)
845
846```
847-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
848| tidb_version() |
849+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
850| Release Version: v5.1.0-20210611
851Edition: Community
852Git Commit Hash: 29bfbb28437609d0a524b7b84e6920dc765978c7
853Git Branch: heads/refs/tags/v5.1.0-20210611
854UTC Build Time: 2021-06-11 07:52:09
855GoVersion: go1.16.4
856Race Enabled: false
857TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
858Check Table Before Drop: false |
859+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
860
861```
862",1, bit char type column metadata is not compatible with mysql bug report please answer these questions before submitting your issue thanks minimal reproduce step required create table pk multi col tmp char collate general ci not null bit not null primary key t nonclustered engine innodb default charset collate general ci select table catalog table catalog table name table name column name column name ordinal position ordinal position column default column default is nullable is nullable data type data type character maximum length character maximum length character octet length character octet length numeric precision numeric precision numeric scale numeric scale datetime precision datetime precision character set name character set name collation name collation name column type column type column key column key extra extra privileges privileges column comment column comment generation expression generation expression from information schema columns where table schema select database and table name pk multi col tmp order by ordinal position what did you expect to see required table catalog table name column name ordinal position column default is nullable data type character maximum length character octet length numeric precision numeric scale datetime precision character set name collation name column type column key extra privileges column comment generation expression def pk multi col tmp null no char null null null general ci char pri select insert update references def pk multi col tmp null no bit null null null null null null bit pri select insert update references what did you see instead required table catalog table name column name ordinal position column default is nullable data type character maximum length character octet length numeric precision numeric scale datetime precision character set name collation name column type column key extra privileges column comment generation expression def pk multi col tmp null no char null null null general ci char pri select insert update references def pk multi col tmp null no bit null null null null null bit unsigned pri select insert update references what is your tidb version required tidb version release version edition community git commit hash git branch heads refs tags utc build time goversion race enabled false tikv min version check table before drop false ,18636795,9100108708.0,IssuesEvent,2019-02-20 07:28:27,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,closed,tidb-server always shows port 3306,type/compatibility,"## Bug Report
864
865Please answer these questions before submitting your issue. Thanks!
866
8671. What did you do?
868
869```
870mysql> show global variables like 'port';
871```
872
8732. What did you expect to see?
874
875```
876mysql> show global variables like 'port';
877+---------------+-------+
878| Variable_name | Value |
879+---------------+-------+
880| port | 4000 |
881+---------------+-------+
8821 row in set (0.00 sec)
883```
884
8853. What did you see instead?
886```
887
888mysql> show global variables like 'port';
889+---------------+-------+
890| Variable_name | Value |
891+---------------+-------+
892| port | 3306 |
893+---------------+-------+
8941 row in set (0.00 sec)
895```
896
897
8984. What version of TiDB are you using (`tidb-server -V` or run `select tidb_version();` on TiDB)?
899```
900mysql> select tidb_version()\G
901*************************** 1. row ***************************
902tidb_version(): Release Version: v3.0.0-beta-55-gb9c5f55cc
903Git Commit Hash: b9c5f55cc0259481734a204a9190a36f0761beea
904Git Branch: accurate-port
905UTC Build Time: 2019-02-19 06:48:36
906GoVersion: go version go1.11.4 linux/amd64
907Race Enabled: false
908TiKV Min Version: 2.1.0-alpha.1-ff3dd160846b7d1aed9079c389fc188f7f5ea13e
909Check Table Before Drop: false
9101 row in set (0.00 sec)
911```
912",True,"tidb-server always shows port 3306 - ## Bug Report
913
914Please answer these questions before submitting your issue. Thanks!
915
9161. What did you do?
917
918```
919mysql> show global variables like 'port';
920```
921
9222. What did you expect to see?
923
924```
925mysql> show global variables like 'port';
926+---------------+-------+
927| Variable_name | Value |
928+---------------+-------+
929| port | 4000 |
930+---------------+-------+
9311 row in set (0.00 sec)
932```
933
9343. What did you see instead?
935```
936
937mysql> show global variables like 'port';
938+---------------+-------+
939| Variable_name | Value |
940+---------------+-------+
941| port | 3306 |
942+---------------+-------+
9431 row in set (0.00 sec)
944```
945
946
9474. What version of TiDB are you using (`tidb-server -V` or run `select tidb_version();` on TiDB)?
948```
949mysql> select tidb_version()\G
950*************************** 1. row ***************************
951tidb_version(): Release Version: v3.0.0-beta-55-gb9c5f55cc
952Git Commit Hash: b9c5f55cc0259481734a204a9190a36f0761beea
953Git Branch: accurate-port
954UTC Build Time: 2019-02-19 06:48:36
955GoVersion: go version go1.11.4 linux/amd64
956Race Enabled: false
957TiKV Min Version: 2.1.0-alpha.1-ff3dd160846b7d1aed9079c389fc188f7f5ea13e
958Check Table Before Drop: false
9591 row in set (0.00 sec)
960```
961",1,tidb server always shows port bug report please answer these questions before submitting your issue thanks what did you do mysql show global variables like port what did you expect to see mysql show global variables like port variable name value port row in set sec what did you see instead mysql show global variables like port variable name value port row in set sec what version of tidb are you using tidb server v or run select tidb version on tidb mysql select tidb version g row tidb version release version beta git commit hash git branch accurate port utc build time goversion go version linux race enabled false tikv min version alpha check table before drop false row in set sec ,19626409,8709680723.0,IssuesEvent,2018-12-06 14:36:51,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,closed,builtin uncompress function ignored the four bytes length,help wanted type/compatibility,"## Bug Report
963
964Please answer these questions before submitting your issue. Thanks!
965
9661. What did you do?
967
968```
969mysql> select uncompress(unhex('02000000789CCB48CDC9C95728CF2FCA4901001A0B045D'));
970```
971
9722. What did you expect to see?
973
974```
975mysql> select uncompress(unhex('02000000789CCB48CDC9C95728CF2FCA4901001A0B045D'));
976+---------------------------------------------------------------------+
977| uncompress(unhex('02000000789CCB48CDC9C95728CF2FCA4901001A0B045D')) |
978+---------------------------------------------------------------------+
979| NULL |
980+---------------------------------------------------------------------+
9811 row in set, 1 warning (0.00 sec)
982
983mysql> show warnings;
984+---------+------+--------------------------------------------------------------------------------------------------+
985| Level | Code | Message |
986+---------+------+--------------------------------------------------------------------------------------------------+
987| Warning | 1258 | ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted) |
988+---------+------+--------------------------------------------------------------------------------------------------+
9891 row in set (0.00 sec)
990```
991
9923. What did you see instead?
993```
994+---------------------------------------------------------------------+
995| uncompress(unhex('02000000789CCB48CDC9C95728CF2FCA4901001A0B045D')) |
996+---------------------------------------------------------------------+
997| hello world |
998+---------------------------------------------------------------------+
9991 row in set (0.01 sec)
1000```
1001
10024. What version of TiDB are you using (`tidb-server -V` or run `select tidb_version();` on TiDB)?
1003
1004```
1005tidb_version(): Release Version: v2.1.0-rc.2-10-gb30dbd0
1006Git Commit Hash: b30dbd06acaab088a1e8fa004e189c651ca08bf1
1007Git Branch: master
1008UTC Build Time: 2018-09-17 01:20:48
1009GoVersion: go version go1.11 linux/amd64
1010Race Enabled: false
1011TiKV Min Version: 2.1.0-alpha.1-ff3dd160846b7d1aed9079c389fc188f7f5ea13e
1012Check Table Before Drop: false
1013```
1014
10155. more info
1016This is found when I try to implement builtin compress and uncompress function in TiKV (https://github.com/tikv/tikv/pull/3856)
1017the first four bytes stored the length of the uncompress string, if it's less than the corrected length (maybe corrupted), MySQL return Null， TiDB just ignore it.",True,"builtin uncompress function ignored the four bytes length - ## Bug Report
1018
1019Please answer these questions before submitting your issue. Thanks!
1020
10211. What did you do?
1022
1023```
1024mysql> select uncompress(unhex('02000000789CCB48CDC9C95728CF2FCA4901001A0B045D'));
1025```
1026
10272. What did you expect to see?
1028
1029```
1030mysql> select uncompress(unhex('02000000789CCB48CDC9C95728CF2FCA4901001A0B045D'));
1031+---------------------------------------------------------------------+
1032| uncompress(unhex('02000000789CCB48CDC9C95728CF2FCA4901001A0B045D')) |
1033+---------------------------------------------------------------------+
1034| NULL |
1035+---------------------------------------------------------------------+
10361 row in set, 1 warning (0.00 sec)
1037
1038mysql> show warnings;
1039+---------+------+--------------------------------------------------------------------------------------------------+
1040| Level | Code | Message |
1041+---------+------+--------------------------------------------------------------------------------------------------+
1042| Warning | 1258 | ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted) |
1043+---------+------+--------------------------------------------------------------------------------------------------+
10441 row in set (0.00 sec)
1045```
1046
10473. What did you see instead?
1048```
1049+---------------------------------------------------------------------+
1050| uncompress(unhex('02000000789CCB48CDC9C95728CF2FCA4901001A0B045D')) |
1051+---------------------------------------------------------------------+
1052| hello world |
1053+---------------------------------------------------------------------+
10541 row in set (0.01 sec)
1055```
1056
10574. What version of TiDB are you using (`tidb-server -V` or run `select tidb_version();` on TiDB)?
1058
1059```
1060tidb_version(): Release Version: v2.1.0-rc.2-10-gb30dbd0
1061Git Commit Hash: b30dbd06acaab088a1e8fa004e189c651ca08bf1
1062Git Branch: master
1063UTC Build Time: 2018-09-17 01:20:48
1064GoVersion: go version go1.11 linux/amd64
1065Race Enabled: false
1066TiKV Min Version: 2.1.0-alpha.1-ff3dd160846b7d1aed9079c389fc188f7f5ea13e
1067Check Table Before Drop: false
1068```
1069
10705. more info
1071This is found when I try to implement builtin compress and uncompress function in TiKV (https://github.com/tikv/tikv/pull/3856)
1072the first four bytes stored the length of the uncompress string, if it's less than the corrected length (maybe corrupted), MySQL return Null， TiDB just ignore it.",1,builtin uncompress function ignored the four bytes length bug report please answer these questions before submitting your issue thanks what did you do mysql select uncompress unhex what did you expect to see mysql select uncompress unhex uncompress unhex null row in set warning sec mysql show warnings level code message warning zlib not enough room in the output buffer probably length of uncompressed data was corrupted row in set sec what did you see instead uncompress unhex hello world row in set sec what version of tidb are you using tidb server v or run select tidb version on tidb tidb version release version rc git commit hash git branch master utc build time goversion go version linux race enabled false tikv min version alpha check table before drop false more info this is found when i try to implement builtin compress and uncompress function in tikv the first four bytes stored the length of the uncompress string if it s less than the corrected length maybe corrupted mysql return null， tidb just ignore it ,110738046,10185915799.0,IssuesEvent,2019-08-10 08:22:46,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,closed,window function: should check fuction's arguments firstly.,help wanted type/bug type/compatibility,"## Bug Report
1074
1075Please answer these questions before submitting your issue. Thanks!
1076
10771. What did you do?
1078If possible, provide a recipe for reproducing the error.
1079
1080```mysql
1081SELECT NTH_VALUE(fieldA, -1) OVER (w1 PARTITION BY fieldB ORDER BY fieldB , fieldA ) AS 'ntile', fieldA, fieldB FROM ( SELECT `pk` AS fieldA, `col_date_key` AS fieldB FROM `table70_int_autoinc` ) as t WINDOW w1 AS ( ORDER BY fieldB ASC, fieldA DESC );
1082```
1083
10842. What did you expect to see?
1085
1086```mysql
1087ERROR 1210 (HY000): Incorrect arguments to nth_value
1088```
1089
10903. What did you see instead?
1091
1092```mysql
1093ERROR 3581 (HY000): A window which depends on another cannot define partitioning.
1094```
10954. What version of TiDB are you using (`tidb-server -V` or run `select tidb_version();` on TiDB)?
1096
1097",True,"window function: should check fuction's arguments firstly. - ## Bug Report
1098
1099Please answer these questions before submitting your issue. Thanks!
1100
11011. What did you do?
1102If possible, provide a recipe for reproducing the error.
1103
1104```mysql
1105SELECT NTH_VALUE(fieldA, -1) OVER (w1 PARTITION BY fieldB ORDER BY fieldB , fieldA ) AS 'ntile', fieldA, fieldB FROM ( SELECT `pk` AS fieldA, `col_date_key` AS fieldB FROM `table70_int_autoinc` ) as t WINDOW w1 AS ( ORDER BY fieldB ASC, fieldA DESC );
1106```
1107
11082. What did you expect to see?
1109
1110```mysql
1111ERROR 1210 (HY000): Incorrect arguments to nth_value
1112```
1113
11143. What did you see instead?
1115
1116```mysql
1117ERROR 3581 (HY000): A window which depends on another cannot define partitioning.
1118```
11194. What version of TiDB are you using (`tidb-server -V` or run `select tidb_version();` on TiDB)?
1120
1121",1,window function should check fuction s arguments firstly bug report please answer these questions before submitting your issue thanks what did you do if possible provide a recipe for reproducing the error mysql select nth value fielda over partition by fieldb order by fieldb fielda as ntile fielda fieldb from select pk as fielda col date key as fieldb from int autoinc as t window as order by fieldb asc fielda desc what did you expect to see mysql error incorrect arguments to nth value what did you see instead mysql error a window which depends on another cannot define partitioning what version of tidb are you using tidb server v or run select tidb version on tidb ,111223289,6254682874.0,IssuesEvent,2017-07-14 03:22:10,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,closed,Support for setting global variable with `on` and `off`,compatibility help wanted rc3.1,"
11231. What did you expect to see?
1124```
1125mysql> set global avoid_temporal_upgrade = on;
1126Query OK, 0 rows affected, 1 warning (0.00 sec)
1127```
1128
11292. What did you see instead?
1130```
1131mysql> set global avoid_temporal_upgrade = on;
1132ERROR 1105 (HY000): line 0 column 38 near """" (total length 38)
1133```
1134",True,"Support for setting global variable with `on` and `off` -
11351. What did you expect to see?
1136```
1137mysql> set global avoid_temporal_upgrade = on;
1138Query OK, 0 rows affected, 1 warning (0.00 sec)
1139```
1140
11412. What did you see instead?
1142```
1143mysql> set global avoid_temporal_upgrade = on;
1144ERROR 1105 (HY000): line 0 column 38 near """" (total length 38)
1145```
1146",1,support for setting global variable with on and off what did you expect to see mysql set global avoid temporal upgrade on query ok rows affected warning sec what did you see instead mysql set global avoid temporal upgrade on error line column near total length ,111473499,6485696846.0,IssuesEvent,2017-08-19 12:58:40,pingcap/tidb,https://api.github.com/repos/pingcap/tidb,opened,support `GROUP BY` modifiers,compatibility enhancement todo,"## 1. What did you do?
1148
1149MySQL and Oracle support [`ROLLUP`](https://dev.mysql.com/doc/refman/5.7/en/group-by-modifiers.html) modifier, sql-server also support `CUBE` and `GROUPING SETS`
1150
1151## 2. What did you expect to see?
1152
1153```sql
1154drop table if exists t;
1155create table t(a bigint, b bigint, c bigint);
1156insert into t values(1, 2, 3), (2, 2, 3), (3, 2, 3);
1157```
1158
1159```sql
1160MySQL > select a, min(b) from t group by a with rollup;
1161+------+--------+
1162| a | min(b) |
1163+------+--------+
1164| 1 | 2 |
1165| 2 | 2 |
1166| 3 | 2 |
1167| NULL | 2 |
1168+------+--------+
11694 rows in set (0.01 sec)
1170```
1171
1172## 3. What did you see instead?
1173
1174```sql
1175TiDB > select a, min(b) from t group by a with rollup;
1176ERROR 1105 (HY000): line 0 column 39 near "" rollup"" (total length 46)
1177```
1178
1179## 4. What version of TiDB are you using (`tidb-server -V`)?
1180
1181```sql
1182TiDB > select tidb_version();
1183+-----------------------------------------------------------------------------------------------------------------------------------------+
1184| tidb_version() |
1185+-----------------------------------------------------------------------------------------------------------------------------------------+
1186| Release Version: 0.8.0
1187Git Commit Hash: 3e1728b4b853c224daa969fcc3d03be5d0860ef4
1188Git Branch: master
1189UTC Build Time: 2017-08-19 12:33:06 |
1190+-----------------------------------------------------------------------------------------------------------------------------------------+
11911 row in set (0.00 sec)
1192```",True,"support `GROUP BY` modifiers - ## 1. What did you do?
1193
1194MySQL and Oracle support [`ROLLUP`](https://dev.mysql.com/doc/refman/5.7/en/group-by-modifiers.html) modifier, sql-server also support `CUBE` and `GROUPING SETS`
1195
1196## 2. What did you expect to see?
1197
1198```sql
1199drop table if exists t;
1200create table t(a bigint, b bigint, c bigint);