This is an automated email from the ASF dual-hosted git repository.
kassiez pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new 5f78d780e89 [update] Fix typo of MySQL Compatibility (#1504)
5f78d780e89 is described below
commit 5f78d780e8989a34eca2df21f9269c6f4c25fc79
Author: KassieZ <139741991+kass...@users.noreply.github.com>
AuthorDate: Wed Dec 11 18:31:38 2024 +0800
[update] Fix typo of MySQL Compatibility (#1504)
## Versions
- [x] dev
- [x] 3.0
- [x] 2.1
- [x] 2.0
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [ ] Checked by AI
- [ ] Test Cases Built
Related PR: https://github.com/apache/doris-website/pull/1498
---
docs/query-data/mysql-compatibility.md | 20 +++++++--------
.../current/query-data/mysql-compatibility.md | 2 +-
.../version-3.0/query-data/mysql-compatibility.md | 2 +-
.../query/query-data/mysql-compatibility.md | 30 +++++++++++-----------
.../version-2.1/query-data/mysql-compatibility.md | 22 ++++++++--------
.../version-3.0/query-data/mysql-compatibility.md | 22 ++++++++--------
6 files changed, 49 insertions(+), 49 deletions(-)
diff --git a/docs/query-data/mysql-compatibility.md
b/docs/query-data/mysql-compatibility.md
index a9557c3e1dd..acd2386b70c 100644
--- a/docs/query-data/mysql-compatibility.md
+++ b/docs/query-data/mysql-compatibility.md
@@ -129,7 +129,7 @@ Doris has several unique data types. Here are the details:
### DDL
-**01 Create Table Syntax in Doris**
+#### 01 Create Table Syntax in Doris
```sql
CREATE TABLE [IF NOT EXISTS] [database.]table
@@ -147,7 +147,7 @@ distribution_desc
[extra_properties]
```
-**02 Differences with MySQL**
+#### 02 Differences with MySQL
| Parameter | Differences from MySQL
|
@@ -163,7 +163,7 @@ distribution_desc
| Properties | Table properties: They differ from MySQL's table
properties, and the syntax for defining table properties also differs from
MySQL. |
-**03 CREATE INDEX**
+#### 03 CREATE INDEX
```sql
CREATE INDEX [IF NOT EXISTS] index_name ON table_name (column [, ...],) [USING
BITMAP];
@@ -173,7 +173,7 @@ CREATE INDEX [IF NOT EXISTS] index_name ON table_name
(column [, ...],) [USING B
- MySQL supports index algorithms such as B+Tree and Hash.
-**04 CREATE VIEW**
+#### 04 CREATE VIEW
```sql
CREATE VIEW [IF NOT EXISTS]
@@ -198,7 +198,7 @@ CREATE MATERIALIZED VIEW (IF NOT EXISTS)?
mvName=multipartIdentifier
- MySQL only supports asynchronous materialized views.
-**05 ALTER TABLE / ALTER INDEX**
+#### 05 ALTER TABLE / ALTER INDEX
The syntax of Doris ALTER is basically the same as that of MySQL.
@@ -208,7 +208,7 @@ The syntax of Doris DROP is basically the same as MySQL.
### DML
-**INSERT**
+#### INSERT
```sql
INSERT INTO table_name
@@ -221,7 +221,7 @@ INSERT INTO table_name
The Doris INSERT syntax is basically the same as MySQL.
-**UPDATE**
+#### UPDATE
```sql
UPDATE target_table [table_alias]
@@ -240,7 +240,7 @@ value:
The Doris UPDATE syntax is basically the same as MySQL, but it should be noted
that the **`WHERE` condition must be added.**
-**Delete**
+#### Delete
```sql
DELETE FROM table_name [table_alias]
@@ -259,9 +259,9 @@ DELETE FROM table_name [table_alias]
This syntax can only be used on the UNIQUE KEY model table.
-The Doris DELTE syntax is basically the same as MySQL. Due to Doris is an
analytical database, deletions can't be too frequent.
+The DELETE syntax in Doris is basically the same as in MySQL. However, since
Doris is an analytical database, deletions cannot be too frequent.
-**SELECT**
+#### SELECT
```sql
SELECT
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-data/mysql-compatibility.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-data/mysql-compatibility.md
index 59409863df5..15685608ec6 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-data/mysql-compatibility.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-data/mysql-compatibility.md
@@ -154,7 +154,7 @@ distribution_desc
| 参数 | 与 MySQL 不同之处
|
| ---------------------- |
------------------------------------------------------------ |
-| column_definition_list | - 字段列表定义，其基本语法与 MySQL 类似，但会额外包含一个聚合类型的操作。<br />-
该聚合类型的操作，主要支持的数据模型为 Aggregate 和 Duplicate。<br />- 在创建表时，MySQL 允许在字段列表定义后添加
Index 等约束，如 Primary Key、Unique Key 等；而 Doris 则是通过定义数据模型来实现对这些约束和计算的支持。 |
+| column_definition_list | - 字段列表定义，其基本语法与 MySQL 类似，但会额外包含一个聚合类型的操作。<br />-
该聚合类型的操作，主要支持的数据模型为 Aggregate Key。<br />- 在创建表时，MySQL 允许在字段列表定义后添加 Index 等约束，如
Primary Key、Unique Key 等；而 Doris 则是通过定义数据模型来实现对这些约束和计算的支持。 |
| index_definition_list | - 索引列表定义，基本语法与 MySQL 类似，支持位图索引、倒排索引和 N-Gram
索引，但是布隆过滤器索引是通过属性设置。<br />- 而 MySQL 支持的 index 有 B+Tree，Hash。 |
| engine_type | - 表引擎类型，可选。<br />- 目前支持的表引擎主要是 OLAP 原生引擎。<br />-
MySQL 支持的存储引擎有：Innodb，MyISAM 等 |
| keys_type | - 数据模型，可选。<br />- 支持的类型包括：1）DUPLICATE
KEY（默认）：其后指定的列为排序列。2）AGGREGATE KEY：其后指定的列为维度列。3）UNIQUE KEY：其后指定的列为主键列。<br />-
MySQL 则没有数据模型的概念。 |
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/query-data/mysql-compatibility.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/query-data/mysql-compatibility.md
index 59409863df5..15685608ec6 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/query-data/mysql-compatibility.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/query-data/mysql-compatibility.md
@@ -154,7 +154,7 @@ distribution_desc
| 参数 | 与 MySQL 不同之处
|
| ---------------------- |
------------------------------------------------------------ |
-| column_definition_list | - 字段列表定义，其基本语法与 MySQL 类似，但会额外包含一个聚合类型的操作。<br />-
该聚合类型的操作，主要支持的数据模型为 Aggregate 和 Duplicate。<br />- 在创建表时，MySQL 允许在字段列表定义后添加
Index 等约束，如 Primary Key、Unique Key 等；而 Doris 则是通过定义数据模型来实现对这些约束和计算的支持。 |
+| column_definition_list | - 字段列表定义，其基本语法与 MySQL 类似，但会额外包含一个聚合类型的操作。<br />-
该聚合类型的操作，主要支持的数据模型为 Aggregate Key。<br />- 在创建表时，MySQL 允许在字段列表定义后添加 Index 等约束，如
Primary Key、Unique Key 等；而 Doris 则是通过定义数据模型来实现对这些约束和计算的支持。 |
| index_definition_list | - 索引列表定义，基本语法与 MySQL 类似，支持位图索引、倒排索引和 N-Gram
索引，但是布隆过滤器索引是通过属性设置。<br />- 而 MySQL 支持的 index 有 B+Tree，Hash。 |
| engine_type | - 表引擎类型，可选。<br />- 目前支持的表引擎主要是 OLAP 原生引擎。<br />-
MySQL 支持的存储引擎有：Innodb，MyISAM 等 |
| keys_type | - 数据模型，可选。<br />- 支持的类型包括：1）DUPLICATE
KEY（默认）：其后指定的列为排序列。2）AGGREGATE KEY：其后指定的列为维度列。3）UNIQUE KEY：其后指定的列为主键列。<br />-
MySQL 则没有数据模型的概念。 |
diff --git a/versioned_docs/version-2.0/query/query-data/mysql-compatibility.md
b/versioned_docs/version-2.0/query/query-data/mysql-compatibility.md
index 77b7bf92d4d..3f296572ae7 100644
--- a/versioned_docs/version-2.0/query/query-data/mysql-compatibility.md
+++ b/versioned_docs/version-2.0/query/query-data/mysql-compatibility.md
@@ -129,9 +129,9 @@ Doris has several unique data types. Here are the details:
### DDL
-**01 Create Table Syntax in Doris**
+#### 01 Create Table Syntax in Doris
-```SQL
+```sql
CREATE TABLE [IF NOT EXISTS] [database.]table
(
column_definition_list
@@ -147,15 +147,15 @@ distribution_desc
[extra_properties]
```
-**02 Differences with MySQL**
+#### 02 Differences with MySQL
- column_definition_list:
- Defines the list of columns, and the basic syntax is similar to MySQL.
However, there are additional operations for **aggregation types**.
- - The **aggregation types** mainly support data models such as AGGREGATE and
Duplicate.
+ - The **aggregation types** mainly support data models such as Aggregate Key.
- - In MySQL, you can define constraints like primary key and unique key after
each column in the column definition list. In Doris, these constraints are
defined and calculated through data models.
+ - In MySQL, you can define constraints like Primary Key and Unique Key after
each column in the column definition list. In Doris, these constraints are
defined and calculated through data models.
- index_definition_list:
@@ -231,7 +231,7 @@ distribution_desc
- Table properties in Doris are different from MySQL, and the syntax for
defining table properties is also different from MySQL.
-**03 Create-Index**
+#### 03 Create-Index
```sql
CREATE INDEX [IF NOT EXISTS] index_name ON table_name (column [, ...],) [USING
BITMAP];
@@ -241,7 +241,7 @@ CREATE INDEX [IF NOT EXISTS] index_name ON table_name
(column [, ...],) [USING B
- MySQL supports index algorithms such as B+Tree and Hash.
-**04 Create-View**
+#### 04 Create-View
```sql
CREATE VIEW [IF NOT EXISTS]
@@ -266,17 +266,17 @@ CREATE MATERIALIZED VIEW (IF NOT EXISTS)?
mvName=multipartIdentifier
- MySQL only supports asynchronous materialized views.
-**05 Alter-Table/Alter-Index**
+#### 05 Alter-Table/Alter-Index
The syntax of Doris ALTER is basically the same as that of MySQL.
-### **Drop-Table/Drop-Index**
+### Drop-Table/Drop-Index
The syntax of Doris DROP is basically the same as MySQL.
-### **DML**
+### DML
-**Insert**
+#### Insert
```sql
INSERT INTO table_name
@@ -289,7 +289,7 @@ INSERT INTO table_name
The Doris INSERT syntax is basically the same as MySQL.
-**Update**
+#### Update
```sql
UPDATE target_table [table_alias]
@@ -308,7 +308,7 @@ value:
The Doris UPDATE syntax is basically the same as MySQL, but it should be noted
that the **`WHERE` condition must be added.**
-**Delete**
+#### Delete
```sql
DELETE FROM table_name [table_alias]
@@ -327,9 +327,9 @@ DELETE FROM table_name [table_alias]
This syntax can only be used on the UNIQUE KEY model table.
-The Doris DELTE syntax is basically the same as MySQL. Due to Doris is an
analytical database, deletions can't be too frequent.
+The DELETE syntax in Doris is basically the same as in MySQL. However, since
Doris is an analytical database, deletions cannot be too frequent.
-**Select**
+#### Select
```sql
SELECT
diff --git a/versioned_docs/version-2.1/query-data/mysql-compatibility.md
b/versioned_docs/version-2.1/query-data/mysql-compatibility.md
index a9557c3e1dd..5dfffc284ee 100644
--- a/versioned_docs/version-2.1/query-data/mysql-compatibility.md
+++ b/versioned_docs/version-2.1/query-data/mysql-compatibility.md
@@ -129,7 +129,7 @@ Doris has several unique data types. Here are the details:
### DDL
-**01 Create Table Syntax in Doris**
+#### 01 Create Table Syntax in Doris
```sql
CREATE TABLE [IF NOT EXISTS] [database.]table
@@ -147,12 +147,12 @@ distribution_desc
[extra_properties]
```
-**02 Differences with MySQL**
+#### 02 Differences with MySQL
| Parameter | Differences from MySQL
|
| ---------------------- |
------------------------------------------------------------ |
-| Column_definition_list | - Field list definition: The basic syntax is
similar to MySQL but includes an additional operation for aggregate types. <br
/>- The aggregate type operation primarily supports Aggregate and Duplicate
data models. <br />- When creating a table, MySQL allows adding constraints
like Index (e.g., Primary Key, Unique Key) after the field list definition,
while Doris supports these constraints and computations by defining data
models. |
+| Column_definition_list | - Field list definition: The basic syntax is
similar to MySQL but includes an additional operation for aggregate types. <br
/>- The aggregate type operation primarily supports Aggregate Key. <br />- When
creating a table, MySQL allows adding constraints like Index (e.g., Primary
Key, Unique Key) after the field list definition, while Doris supports these
constraints and computations by defining data models. |
| Index_definition_list | - Index list definition: The basic syntax is
similar to MySQL, supporting bitmap indexes, inverted indexes, and N-Gram
indexes, but Bloom filter indexes are set through properties. <br />- MySQL
supports B+Tree and Hash indexes. |
| Engine_type | - Table engine type: Optional. <br />- The
currently supported table engine is mainly the OLAP native engine. <br />-
MySQL supports storage engines such as Innodb, MyISAM, etc. |
| Keys_type | - Data model: Optional. <br />- Supported types
include: 1) DUPLICATE KEY (default): The specified columns are sort columns. 2)
AGGREGATE KEY: The specified columns are dimension columns. 3) UNIQUE KEY: The
specified columns are primary key columns. <br />- MySQL does not have the
concept of a data model. |
@@ -163,7 +163,7 @@ distribution_desc
| Properties | Table properties: They differ from MySQL's table
properties, and the syntax for defining table properties also differs from
MySQL. |
-**03 CREATE INDEX**
+#### 03 CREATE INDEX
```sql
CREATE INDEX [IF NOT EXISTS] index_name ON table_name (column [, ...],) [USING
BITMAP];
@@ -173,7 +173,7 @@ CREATE INDEX [IF NOT EXISTS] index_name ON table_name
(column [, ...],) [USING B
- MySQL supports index algorithms such as B+Tree and Hash.
-**04 CREATE VIEW**
+#### 04 CREATE VIEW
```sql
CREATE VIEW [IF NOT EXISTS]
@@ -198,7 +198,7 @@ CREATE MATERIALIZED VIEW (IF NOT EXISTS)?
mvName=multipartIdentifier
- MySQL only supports asynchronous materialized views.
-**05 ALTER TABLE / ALTER INDEX**
+#### 05 ALTER TABLE / ALTER INDEX
The syntax of Doris ALTER is basically the same as that of MySQL.
@@ -208,7 +208,7 @@ The syntax of Doris DROP is basically the same as MySQL.
### DML
-**INSERT**
+#### INSERT
```sql
INSERT INTO table_name
@@ -221,7 +221,7 @@ INSERT INTO table_name
The Doris INSERT syntax is basically the same as MySQL.
-**UPDATE**
+#### UPDATE
```sql
UPDATE target_table [table_alias]
@@ -240,7 +240,7 @@ value:
The Doris UPDATE syntax is basically the same as MySQL, but it should be noted
that the **`WHERE` condition must be added.**
-**Delete**
+#### Delete
```sql
DELETE FROM table_name [table_alias]
@@ -259,9 +259,9 @@ DELETE FROM table_name [table_alias]
This syntax can only be used on the UNIQUE KEY model table.
-The Doris DELTE syntax is basically the same as MySQL. Due to Doris is an
analytical database, deletions can't be too frequent.
+The DELETE syntax in Doris is basically the same as in MySQL. However, since
Doris is an analytical database, deletions cannot be too frequent.
-**SELECT**
+#### Select
```sql
SELECT
diff --git a/versioned_docs/version-3.0/query-data/mysql-compatibility.md
b/versioned_docs/version-3.0/query-data/mysql-compatibility.md
index a9557c3e1dd..5dfffc284ee 100644
--- a/versioned_docs/version-3.0/query-data/mysql-compatibility.md
+++ b/versioned_docs/version-3.0/query-data/mysql-compatibility.md
@@ -129,7 +129,7 @@ Doris has several unique data types. Here are the details:
### DDL
-**01 Create Table Syntax in Doris**
+#### 01 Create Table Syntax in Doris
```sql
CREATE TABLE [IF NOT EXISTS] [database.]table
@@ -147,12 +147,12 @@ distribution_desc
[extra_properties]
```
-**02 Differences with MySQL**
+#### 02 Differences with MySQL
| Parameter | Differences from MySQL
|
| ---------------------- |
------------------------------------------------------------ |
-| Column_definition_list | - Field list definition: The basic syntax is
similar to MySQL but includes an additional operation for aggregate types. <br
/>- The aggregate type operation primarily supports Aggregate and Duplicate
data models. <br />- When creating a table, MySQL allows adding constraints
like Index (e.g., Primary Key, Unique Key) after the field list definition,
while Doris supports these constraints and computations by defining data
models. |
+| Column_definition_list | - Field list definition: The basic syntax is
similar to MySQL but includes an additional operation for aggregate types. <br
/>- The aggregate type operation primarily supports Aggregate Key. <br />- When
creating a table, MySQL allows adding constraints like Index (e.g., Primary
Key, Unique Key) after the field list definition, while Doris supports these
constraints and computations by defining data models. |
| Index_definition_list | - Index list definition: The basic syntax is
similar to MySQL, supporting bitmap indexes, inverted indexes, and N-Gram
indexes, but Bloom filter indexes are set through properties. <br />- MySQL
supports B+Tree and Hash indexes. |
| Engine_type | - Table engine type: Optional. <br />- The
currently supported table engine is mainly the OLAP native engine. <br />-
MySQL supports storage engines such as Innodb, MyISAM, etc. |
| Keys_type | - Data model: Optional. <br />- Supported types
include: 1) DUPLICATE KEY (default): The specified columns are sort columns. 2)
AGGREGATE KEY: The specified columns are dimension columns. 3) UNIQUE KEY: The
specified columns are primary key columns. <br />- MySQL does not have the
concept of a data model. |
@@ -163,7 +163,7 @@ distribution_desc
| Properties | Table properties: They differ from MySQL's table
properties, and the syntax for defining table properties also differs from
MySQL. |
-**03 CREATE INDEX**
+#### 03 CREATE INDEX
```sql
CREATE INDEX [IF NOT EXISTS] index_name ON table_name (column [, ...],) [USING
BITMAP];
@@ -173,7 +173,7 @@ CREATE INDEX [IF NOT EXISTS] index_name ON table_name
(column [, ...],) [USING B
- MySQL supports index algorithms such as B+Tree and Hash.
-**04 CREATE VIEW**
+#### 04 CREATE VIEW
```sql
CREATE VIEW [IF NOT EXISTS]
@@ -198,7 +198,7 @@ CREATE MATERIALIZED VIEW (IF NOT EXISTS)?
mvName=multipartIdentifier
- MySQL only supports asynchronous materialized views.
-**05 ALTER TABLE / ALTER INDEX**
+#### 05 ALTER TABLE / ALTER INDEX
The syntax of Doris ALTER is basically the same as that of MySQL.
@@ -208,7 +208,7 @@ The syntax of Doris DROP is basically the same as MySQL.
### DML
-**INSERT**
+#### INSERT
```sql
INSERT INTO table_name
@@ -221,7 +221,7 @@ INSERT INTO table_name
The Doris INSERT syntax is basically the same as MySQL.
-**UPDATE**
+#### UPDATE
```sql
UPDATE target_table [table_alias]
@@ -240,7 +240,7 @@ value:
The Doris UPDATE syntax is basically the same as MySQL, but it should be noted
that the **`WHERE` condition must be added.**
-**Delete**
+#### Delete
```sql
DELETE FROM table_name [table_alias]
@@ -259,9 +259,9 @@ DELETE FROM table_name [table_alias]
This syntax can only be used on the UNIQUE KEY model table.
-The Doris DELTE syntax is basically the same as MySQL. Due to Doris is an
analytical database, deletions can't be too frequent.
+The DELETE syntax in Doris is basically the same as in MySQL. However, since
Doris is an analytical database, deletions cannot be too frequent.
-**SELECT**
+#### Select
```sql
SELECT
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
