parser : support drop sequence syntax.#680
Merged
tangenta merged 4 commits intopingcap:masterfrom Dec 16, 2019
Merged
Conversation
ghost
requested review from
Codecov Report
@@ Coverage Diff @@
## master #680 +/- ##
=========================================
+ Coverage 79.82% 80.13% +0.3%
=========================================
Files 37 33 -4
Lines 13596 13030 -566
=========================================
- Hits 10853 10441 -412
+ Misses 2100 1967 -133
+ Partials 643 622 -21
Continue to review full report at Codecov.
|
AilinKid
force-pushed
the
delet_sequence
branch
from
cedfab3 to
bf3ec8e
Compare
This was referenced Sep 10, 2020
tiancaiamao
pushed a commit
to tiancaiamao/parser
that referenced
this pull request
Apr 27, 2021
lyonzhi
pushed a commit
to lyonzhi/parser
that referenced
this pull request
Apr 25, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
TiDB are compatible with MySQL's protocol, we should be also compatible with SEQUENCE implementation of MariaDB cause MySQL is absent from it.
Linked with sequence project, this PR try to support drop sequence syntax.
What is changed and how it works?
SHOW CREATE SEQUENCE sequence_name;ALTER SEQUENCE [IF EXISTS] sequence_name [ INCREMENT [ BY | = ] increment ] [ MINVALUE [=] minvalue | NO MINVALUE | NOMINVALUE ] [ MAXVALUE [=] maxvalue | NO MAXVALUE | NOMAXVALUE ] [ START [ WITH | = ] start ] [ CACHE [=] cache ] [ [ NO ] CYCLE ] [ RESTART [[WITH | =] restart];DROP [TEMPORARY] SEQUENCE [IF EXISTS] sequence_name [, sequence_name] ...Sequence Function (need discussion)Check List
Tests