Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions sql-statements/sql-statement-drop-sequence.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,6 @@ The `DROP SEQUENCE` statement drops the sequence object in TiDB.

![DropSequenceStmt](/media/sqlgram/DropSequenceStmt.png)

**OptTemporary:**

![OptTemporary](/media/sqlgram/OptTemporary.png)

**IfExists:**

![IfExists](/media/sqlgram/IfExists.png)
Expand All @@ -27,6 +23,10 @@ The `DROP SEQUENCE` statement drops the sequence object in TiDB.

![TableNameList](/media/sqlgram/TableNameList.png)

**TableName:**

![TableName](/media/sqlgram/TableName.png)

## Examples

{{< copyable "sql" >}}
Expand All @@ -51,7 +51,7 @@ Query OK, 0 rows affected (0.03 sec)

## MySQL compatibility

Currently, MySQL does not have the sequence option. The TiDB sequence is borrowed from MariaDB. Except for the `SETVAL` function, all other functions have the same progressions with those functions of MariaDB.
Currently, sequence object is not supported by MySQL.

## See also

Expand Down
11 changes: 4 additions & 7 deletions sql-statements/sql-statement-show-character-set.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,13 +11,9 @@ This statement provides a static list of available character sets in TiDB. The o

## Synopsis

**ShowStmt:**
**ShowCharsetStmt:**

![ShowStmt](/media/sqlgram/ShowStmt.png)

**ShowTargetFilterable:**

![ShowTargetFilterable](/media/sqlgram/ShowTargetFilterable.png)
![ShowCharsetStmt](/media/sqlgram/ShowCharsetStmt.png)

**CharsetKw:**

Expand All @@ -41,8 +37,9 @@ mysql> SHOW CHARACTER SET;

## MySQL compatibility

This statement is understood to be fully compatible with MySQL. Any compatibility differences should be [reported via an issue](/report-issue.md) on GitHub.
The usage of this statement is understood to be fully compatible with MySQL. However, charsets in TiDB may have different default collations compared with MySQL. For details, refer to [Compatibility with MySQL](/mysql-compatibility.md). Any other compatibility differences should be [reported via an issue](/report-issue.md) on GitHub.

## See also

* [SHOW COLLATION](/sql-statements/sql-statement-show-collation.md)
* [Character Set and Collation](/character-set-and-collation.md)
Loading