kennytm
kennytm
TiDB does not support functions or stored procedures as of 4.0, so `pingcap/parser` currently have not implemented the syntax around these features.
Potential solutions 1. Configure a bot which automatically do the rebase-and-squash operation, which resolves the conflict by running `goyacc`. 2. Configure a bot which performs the merge and resolve conflict...
@zhouqiang-cl Ping. Could we raise this again to the EE-team? SIG-DDL can't do anything to fix this, since only you guys can add the bots (web hooks), and also pingcap...
Follow MySQL's behavior on doubt. ``` mysql> SELECT @@autocommit limit 1; +--------------+ | @@autocommit | +--------------+ | 1 | +--------------+ 1 row in set (0.00 sec) mysql> select 1 where...
Hi. Currently you can't get the ColumnInfo/TableInfo from the `pingcap/parser` package alone, because these also record states exclusive for TiDB. If you already have a running TiDB instance, you can...
I don't see any point *disabling* support of DISTINCT. We provide the correct result with DISTINCT, compatible with PostgreSQL. ```sql create table a (a int); insert into a values (1),...
this should also recognize `replace into`. the keyword `values` can also be `value`.
Several issues are wrongly duped into here. So for record, a `/*+ … */` appearing in the wrong place currently causes syntax error which should not happen: ```sql SELECT 1...
this should be fixed in #711.
@kolbe it is a different bug (the error is the unexpected "hint token" `/*+ …. */`, the content `xyz` is irrelevant).