From 28d11196f2293649aed485f6ce26d801997542ee Mon Sep 17 00:00:00 2001 From: HOHO <591310381@qq.com> Date: Thu, 11 Jan 2024 18:15:13 +0800 Subject: [PATCH 1/6] Update partitioned-table.md --- partitioned-table.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/partitioned-table.md b/partitioned-table.md index e82952aaf13e4..aa5b64bdf7b10 100644 --- a/partitioned-table.md +++ b/partitioned-table.md @@ -295,7 +295,7 @@ ALTER TABLE table_name LAST PARTITION LESS THAN () - The INTERVAL partitioning feature only involves the `CREATE/ALTER TABLE` syntax. There is no change in metadata, so tables created or altered with the new syntax are still MySQL-compatible. - There is no change in the output format of `SHOW CREATE TABLE` to keep MySQL compatibility. - The new `ALTER` syntax applies to existing tables conforming to INTERVAL. You do not need to create these tables with the `INTERVAL` syntax. -- For `RANGE COLUMNS`, only integer, date, and datetime column types are supported. +- For `RANGE COLUMNS`, only one column that is integer, date, and datetime types is supported as partitioning key. ### List partitioning From 56042171310645c26a693554268b9e017ed18847 Mon Sep 17 00:00:00 2001 From: HOHO <591310381@qq.com> Date: Thu, 11 Jan 2024 19:09:10 +0800 Subject: [PATCH 2/6] Update partitioned-table.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Daniël van Eeden --- partitioned-table.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/partitioned-table.md b/partitioned-table.md index aa5b64bdf7b10..d664b85dbfc62 100644 --- a/partitioned-table.md +++ b/partitioned-table.md @@ -295,7 +295,7 @@ ALTER TABLE table_name LAST PARTITION LESS THAN () - The INTERVAL partitioning feature only involves the `CREATE/ALTER TABLE` syntax. There is no change in metadata, so tables created or altered with the new syntax are still MySQL-compatible. - There is no change in the output format of `SHOW CREATE TABLE` to keep MySQL compatibility. - The new `ALTER` syntax applies to existing tables conforming to INTERVAL. You do not need to create these tables with the `INTERVAL` syntax. -- For `RANGE COLUMNS`, only one column that is integer, date, and datetime types is supported as partitioning key. +- For `RANGE COLUMNS`, only one column that is an integer, date, or datetime types is supported as partitioning key. ### List partitioning From 8967bf9058618de9690439b959dc4e59e577e65d Mon Sep 17 00:00:00 2001 From: HOHO <591310381@qq.com> Date: Fri, 19 Jan 2024 12:01:30 +0800 Subject: [PATCH 3/6] Update partitioned-table.md Co-authored-by: Grace Cai --- partitioned-table.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/partitioned-table.md b/partitioned-table.md index d664b85dbfc62..97c71f29c4e79 100644 --- a/partitioned-table.md +++ b/partitioned-table.md @@ -295,7 +295,7 @@ ALTER TABLE table_name LAST PARTITION LESS THAN () - The INTERVAL partitioning feature only involves the `CREATE/ALTER TABLE` syntax. There is no change in metadata, so tables created or altered with the new syntax are still MySQL-compatible. - There is no change in the output format of `SHOW CREATE TABLE` to keep MySQL compatibility. - The new `ALTER` syntax applies to existing tables conforming to INTERVAL. You do not need to create these tables with the `INTERVAL` syntax. -- For `RANGE COLUMNS`, only one column that is an integer, date, or datetime types is supported as partitioning key. +- For `RANGE COLUMNS` partitioning, only one column that is in the integer, date, or datetime type can be used as the partitioning key. ### List partitioning From 4c1d970a5f6100e4b0bc01ef9325f847eed93283 Mon Sep 17 00:00:00 2001 From: HOHO <591310381@qq.com> Date: Sun, 21 Jan 2024 19:39:36 +0800 Subject: [PATCH 4/6] Update partitioned-table.md Co-authored-by: Grace Cai --- partitioned-table.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/partitioned-table.md b/partitioned-table.md index 97c71f29c4e79..9564f2d47a2ef 100644 --- a/partitioned-table.md +++ b/partitioned-table.md @@ -295,7 +295,7 @@ ALTER TABLE table_name LAST PARTITION LESS THAN () - The INTERVAL partitioning feature only involves the `CREATE/ALTER TABLE` syntax. There is no change in metadata, so tables created or altered with the new syntax are still MySQL-compatible. - There is no change in the output format of `SHOW CREATE TABLE` to keep MySQL compatibility. - The new `ALTER` syntax applies to existing tables conforming to INTERVAL. You do not need to create these tables with the `INTERVAL` syntax. -- For `RANGE COLUMNS` partitioning, only one column that is in the integer, date, or datetime type can be used as the partitioning key. +- If you want to use the `INTERVAL` syntax for `RANGE COLUMNS` partitioning, only one column that is in the integer, date, or datetime type can be specified as the partitioning key. ### List partitioning From 02dd08714bd7ab121813394c209eaf7f2c72a942 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Tue, 23 Jan 2024 16:02:21 +0800 Subject: [PATCH 5/6] wording updates --- partitioned-table.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/partitioned-table.md b/partitioned-table.md index 9564f2d47a2ef..d3c415976af45 100644 --- a/partitioned-table.md +++ b/partitioned-table.md @@ -295,7 +295,7 @@ ALTER TABLE table_name LAST PARTITION LESS THAN () - The INTERVAL partitioning feature only involves the `CREATE/ALTER TABLE` syntax. There is no change in metadata, so tables created or altered with the new syntax are still MySQL-compatible. - There is no change in the output format of `SHOW CREATE TABLE` to keep MySQL compatibility. - The new `ALTER` syntax applies to existing tables conforming to INTERVAL. You do not need to create these tables with the `INTERVAL` syntax. -- If you want to use the `INTERVAL` syntax for `RANGE COLUMNS` partitioning, only one column that is in the integer, date, or datetime type can be specified as the partitioning key. +- If you want to use the `INTERVAL` syntax for `RANGE COLUMNS` partitioning, only a single column that is in the integer, date, or datetime type can be specified as the partitioning key. ### List partitioning From 7cdb26a85eee3b464941ef7368223a20fd8e3ba5 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Tue, 23 Jan 2024 16:33:44 +0800 Subject: [PATCH 6/6] Update partitioned-table.md Co-authored-by: xixirangrang --- partitioned-table.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/partitioned-table.md b/partitioned-table.md index d3c415976af45..1b80da4c7beb1 100644 --- a/partitioned-table.md +++ b/partitioned-table.md @@ -295,7 +295,7 @@ ALTER TABLE table_name LAST PARTITION LESS THAN () - The INTERVAL partitioning feature only involves the `CREATE/ALTER TABLE` syntax. There is no change in metadata, so tables created or altered with the new syntax are still MySQL-compatible. - There is no change in the output format of `SHOW CREATE TABLE` to keep MySQL compatibility. - The new `ALTER` syntax applies to existing tables conforming to INTERVAL. You do not need to create these tables with the `INTERVAL` syntax. -- If you want to use the `INTERVAL` syntax for `RANGE COLUMNS` partitioning, only a single column that is in the integer, date, or datetime type can be specified as the partitioning key. +- To use the `INTERVAL` syntax for `RANGE COLUMNS` partitioning, you can only specify a single column in the `INTEGER`, `DATE`, or `DATETIME` type as the partitioning key. ### List partitioning