From 1a1f3f1372aec7d7b447f132ca6223f1959d577d Mon Sep 17 00:00:00 2001 From: Frank945946 <108602632+Frank945946@users.noreply.github.com> Date: Fri, 23 Aug 2024 16:20:35 +0800 Subject: [PATCH 1/6] Update generated-columns.md --- generated-columns.md | 1 + 1 file changed, 1 insertion(+) diff --git a/generated-columns.md b/generated-columns.md index 56238ddd2c034..37ce26208a5db 100644 --- a/generated-columns.md +++ b/generated-columns.md @@ -154,4 +154,5 @@ The current limitations of JSON and generated columns are as follows: - You can neither convert a stored generated column to a normal column through the `ALTER TABLE` statement nor convert a normal column to a stored generated column. - You cannot modify the expression of a stored generated column through the `ALTER TABLE` statement. - Not all [JSON functions](/functions-and-operators/json-functions.md) are supported; +- The [NULLIF functions](/control-flow-functions#nullif.md) is not supported. You can use the [CASE function](/control-flow-functions#case.md)as an alternative. - Currently, the generated column index replacement rule is valid only when the generated column is a virtual generated column. It is not valid on the stored generated column, but the index can still be used by directly using the generated column itself. From 24a1cfc40143947e468c873b7782ea18d433bba8 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Mon, 2 Sep 2024 12:02:17 +0800 Subject: [PATCH 2/6] Update generated-columns.md --- generated-columns.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/generated-columns.md b/generated-columns.md index 37ce26208a5db..839ac20dc857a 100644 --- a/generated-columns.md +++ b/generated-columns.md @@ -154,5 +154,5 @@ The current limitations of JSON and generated columns are as follows: - You can neither convert a stored generated column to a normal column through the `ALTER TABLE` statement nor convert a normal column to a stored generated column. - You cannot modify the expression of a stored generated column through the `ALTER TABLE` statement. - Not all [JSON functions](/functions-and-operators/json-functions.md) are supported; -- The [NULLIF functions](/control-flow-functions#nullif.md) is not supported. You can use the [CASE function](/control-flow-functions#case.md)as an alternative. +- The [`NULLIF()` function](/control-flow-functions.md#nullif) is not supported. You can use the [`CASE` function](/control-flow-functions.md#case) as an alternative. - Currently, the generated column index replacement rule is valid only when the generated column is a virtual generated column. It is not valid on the stored generated column, but the index can still be used by directly using the generated column itself. From 14509c989a530729b4d3d2ae5415c26ed8fc91f7 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Mon, 2 Sep 2024 12:03:37 +0800 Subject: [PATCH 3/6] Update generated-columns.md --- generated-columns.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/generated-columns.md b/generated-columns.md index 839ac20dc857a..76d108b22c003 100644 --- a/generated-columns.md +++ b/generated-columns.md @@ -154,5 +154,5 @@ The current limitations of JSON and generated columns are as follows: - You can neither convert a stored generated column to a normal column through the `ALTER TABLE` statement nor convert a normal column to a stored generated column. - You cannot modify the expression of a stored generated column through the `ALTER TABLE` statement. - Not all [JSON functions](/functions-and-operators/json-functions.md) are supported; -- The [`NULLIF()` function](/control-flow-functions.md#nullif) is not supported. You can use the [`CASE` function](/control-flow-functions.md#case) as an alternative. +- The [`NULLIF()` function](/control-flow-functions.md#nullif) is not supported. You can use the [`CASE` function](/control-flow-functions.md#case) instead. - Currently, the generated column index replacement rule is valid only when the generated column is a virtual generated column. It is not valid on the stored generated column, but the index can still be used by directly using the generated column itself. From 89b2851e814f0add7aa97c898b77d4fefaea6670 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Mon, 2 Sep 2024 13:53:53 +0800 Subject: [PATCH 4/6] Update generated-columns.md --- generated-columns.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/generated-columns.md b/generated-columns.md index 76d108b22c003..31886cd3c8628 100644 --- a/generated-columns.md +++ b/generated-columns.md @@ -154,5 +154,5 @@ The current limitations of JSON and generated columns are as follows: - You can neither convert a stored generated column to a normal column through the `ALTER TABLE` statement nor convert a normal column to a stored generated column. - You cannot modify the expression of a stored generated column through the `ALTER TABLE` statement. - Not all [JSON functions](/functions-and-operators/json-functions.md) are supported; -- The [`NULLIF()` function](/control-flow-functions.md#nullif) is not supported. You can use the [`CASE` function](/control-flow-functions.md#case) instead. +- The [`NULLIF()` function]((/functions-and-operators/control-flow-functions.md#nullif) is not supported. You can use the [`CASE` function]((/functions-and-operators/control-flow-functions.md#case) instead. - Currently, the generated column index replacement rule is valid only when the generated column is a virtual generated column. It is not valid on the stored generated column, but the index can still be used by directly using the generated column itself. From ffa88b01a915e6a65c054d36550df4a946eeccaf Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Mon, 2 Sep 2024 14:04:17 +0800 Subject: [PATCH 5/6] Update generated-columns.md --- generated-columns.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/generated-columns.md b/generated-columns.md index 31886cd3c8628..0752d942d73c0 100644 --- a/generated-columns.md +++ b/generated-columns.md @@ -154,5 +154,5 @@ The current limitations of JSON and generated columns are as follows: - You can neither convert a stored generated column to a normal column through the `ALTER TABLE` statement nor convert a normal column to a stored generated column. - You cannot modify the expression of a stored generated column through the `ALTER TABLE` statement. - Not all [JSON functions](/functions-and-operators/json-functions.md) are supported; -- The [`NULLIF()` function]((/functions-and-operators/control-flow-functions.md#nullif) is not supported. You can use the [`CASE` function]((/functions-and-operators/control-flow-functions.md#case) instead. +- The [`NULLIF()` function](/functions-and-operators/control-flow-functions.md#nullif) is not supported. You can use the [`CASE` function]((/functions-and-operators/control-flow-functions.md#case) instead. - Currently, the generated column index replacement rule is valid only when the generated column is a virtual generated column. It is not valid on the stored generated column, but the index can still be used by directly using the generated column itself. From fd8489af204ad100c0d71921665cec9fa46c8180 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Mon, 2 Sep 2024 14:17:56 +0800 Subject: [PATCH 6/6] Update generated-columns.md Co-authored-by: Lilian Lee --- generated-columns.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/generated-columns.md b/generated-columns.md index 0752d942d73c0..13d962ab918e7 100644 --- a/generated-columns.md +++ b/generated-columns.md @@ -153,6 +153,6 @@ The current limitations of JSON and generated columns are as follows: - You cannot add a stored generated column through `ALTER TABLE`. - You can neither convert a stored generated column to a normal column through the `ALTER TABLE` statement nor convert a normal column to a stored generated column. - You cannot modify the expression of a stored generated column through the `ALTER TABLE` statement. -- Not all [JSON functions](/functions-and-operators/json-functions.md) are supported; -- The [`NULLIF()` function](/functions-and-operators/control-flow-functions.md#nullif) is not supported. You can use the [`CASE` function]((/functions-and-operators/control-flow-functions.md#case) instead. +- Not all [JSON functions](/functions-and-operators/json-functions.md) are supported. +- The [`NULLIF()` function](/functions-and-operators/control-flow-functions.md#nullif) is not supported. You can use the [`CASE` function](/functions-and-operators/control-flow-functions.md#case) instead. - Currently, the generated column index replacement rule is valid only when the generated column is a virtual generated column. It is not valid on the stored generated column, but the index can still be used by directly using the generated column itself.