parser: fix tableAlias in DeleteStmt

[spongedu]

What problem does this PR solve?

#189 tried to implement Restore for DeleteStmt, but there's a little mistake: the .* syntax should not be defined as part of TableName. It should be defined as an independent term and be used in DeleteStmt only, as is defined in MySQL Parser

This pr seems fix #357 as well.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

Code changes

N / A

Side effects

N / A

Related changes

• Need to cherry-pick to the release branch
• Need to update the documentation
• Need to be included in the release note

[codecov]

Codecov Report

Merging #521 into master will decrease coverage by 8.23%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #521      +/-   ##
==========================================
- Coverage      80%   71.76%   -8.24%     
==========================================
  Files          32       32              
  Lines       12696     7813    -4883     
==========================================
- Hits        10157     5607    -4550     
+ Misses       1935     1676     -259     
+ Partials      604      530      -74

Impacted Files	Coverage Δ
parser.go	70.58% <ø> (-22.36%)	⬇️
ast/misc.go	74.46% <0%> (-1.45%)	⬇️
ast/dml.go	73.56% <0%> (-0.41%)	⬇️
ast/functions.go	76.74% <0%> (-0.33%)	⬇️
ast/expressions.go	72.52% <0%> (-0.27%)	⬇️
goyacc/main.go	0% <0%> (ø)	⬆️
charset/charset.go	87.01% <0%> (ø)	⬆️
yy_parser.go	83.46% <0%> (ø)	⬆️
mysql/const.go	25.27% <0%> (ø)	⬆️
... and 5 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5173e98...11f5ac6. Read the comment docs.

[kennytm]

CREATE table .t (a bigint)

Since this is invalid in MySQL 8.0 I don't think we want to support this. WDYT @leoppro @tangenta

[spongedu]

CREATE table .t (a bigint)

Since this is invalid in MySQL 8.0 I don't think we want to support this. WDYT @leoppro @tangenta

But currently TiDB and the Parser is mainly MySQL 5.7 compatible, and it seems long way for TiDB and the users to migrate to MySQL 8.0's behavior. I'm not sure if we should ignore the MySQL 5.7 compatible issues now....
BTW, What's the compatibility strategy do we hold for the Parser now? As I've mentioned in #506 , currently the Parser seems a mixture of MySQL 5.7, MySQL 8.0 and MariaDB. @kennytm what do you think about this?

[kennytm]

@spongedu We intend to be eventually compatible with 8.0 (pingcap/tidb#7968), so if a missing 5.7 feature is deprecated or removed on 8.0 we won't support it (unless it is trivial). Example of such rejected feature requests: pingcap/tidb#3685, pingcap/tidb#4025, pingcap/tidb#10092.

[spongedu]

@spongedu We intend to be eventually compatible with 8.0 (pingcap/tidb#7968), so if a missing 5.7 feature is deprecated or removed on 8.0 we won't support it (unless it is trivial). Example of such rejected feature requests: pingcap/tidb#3685, pingcap/tidb#4025, pingcap/tidb#10092.

OK, I've revert this change. PTAL :) @kennytm @leoppro

[spongedu]

@kennytm @leoppro @tangenta PTAL

[kennytm]

Rest LGTM

[spongedu]

@crazycs520 PTAL :)

[SunRunAway]

LGTM

[SunRunAway]

@spongedu Please help resolve the conflicting files.

[spongedu]

@SunRunAway PTAL :)

[sre-bot]

/run-all-tests