Skip to content

Commit 32088b8

Browse files
authored
Align 6 PRs from docs-cn (#7887)
1 parent fc017f9 commit 32088b8

File tree

5 files changed

+4
-5
lines changed

5 files changed

+4
-5
lines changed

data-type-string.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ TiDB supports all the MySQL string types, including `CHAR`, `VARCHAR`, `BINARY`,
1212

1313
### `CHAR` type
1414

15-
`CHAR` is a fixed length string. Values stored as `CHAR` are right-padded with spaces to the specified length. M represents the column-length in characters (not bytes). The range of M is 0 to 255:
15+
`CHAR` is a fixed length string. M represents the column-length in characters (not bytes). The range of M is 0 to 255. Different from the `VARCHAR` type, when data is inserted into a `CHAR` column, the trailing spaces are truncated.
1616

1717
```sql
1818
[NATIONAL] CHAR[(M)] [CHARACTER SET charset_name] [COLLATE collation_name]

mysql-compatibility.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ TiDB supports storage engine abstraction similar to MySQL, but you need to speci
147147

148148
TiDB supports most [SQL modes](/sql-mode.md):
149149

150-
- The compatibility modes, such as `ORACLE` and `POSTGRESQL` are parsed but ignored. Compatibility modes are deprecated in MySQL 5.7 and removed in MySQL 8.0.
150+
- The compatibility modes, such as `Oracle` and `PostgreSQL` are parsed but ignored. Compatibility modes are deprecated in MySQL 5.7 and removed in MySQL 8.0.
151151
- The `ONLY_FULL_GROUP_BY` mode has minor [semantic differences](/functions-and-operators/aggregate-group-by-functions.md#differences-from-mysql) from MySQL 5.7.
152152
- The `NO_DIR_IN_CREATE` and `NO_ENGINE_SUBSTITUTION` SQL modes in MySQL are accepted for compatibility, but are not applicable to TiDB.
153153

sql-plan-replayer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Based on `sql-statement`, TiDB sorts out and exports the following on-site infor
4343
```sql
4444
use test;
4545
create table t(a int, b int);
46-
insert into t valuse(1,1), (2, 2), (3, 3);
46+
insert into t values(1,1), (2, 2), (3, 3);
4747
analyze table t;
4848

4949
plan replayer dump explain select * from t;

sql-statements/sql-statement-create-index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ You can also specify the expression index when you create the table:
127127
{{< copyable "sql" >}}
128128

129129
```sql
130-
CREATE TABLE t1(col1 char(10), col2 char(10), key index((lower(col1))));
130+
CREATE TABLE t1(col1 char(10), col2 char(10), index((lower(col1))));
131131
```
132132

133133
> **Note**

sql-statements/sql-statement-explain.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -245,7 +245,6 @@ If the `dot` program is not installed on your computer, copy the result to [this
245245

246246
* Both the format of `EXPLAIN` and the potential execution plans in TiDB differ substaintially from MySQL.
247247
* TiDB does not support the `FORMAT=JSON` or `FORMAT=TREE` options.
248-
* TiDB does not currently support `EXPLAIN` for insert statements.
249248

250249
### `EXPLAIN FOR CONNECTION`
251250

0 commit comments

Comments
 (0)