From 7b9d81af845b0cb0dcd1f7851e9e7b2de12e89b5 Mon Sep 17 00:00:00 2001 From: Alexey Milovidov Date: Mon, 16 May 2022 04:28:39 +0300 Subject: [PATCH] Update grouparray.md --- .../sql-reference/aggregate-functions/reference/grouparray.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/en/sql-reference/aggregate-functions/reference/grouparray.md b/docs/en/sql-reference/aggregate-functions/reference/grouparray.md index 83432ff3d39..003df467238 100644 --- a/docs/en/sql-reference/aggregate-functions/reference/grouparray.md +++ b/docs/en/sql-reference/aggregate-functions/reference/grouparray.md @@ -14,6 +14,7 @@ The second version (with the `max_size` parameter) limits the size of the result In some cases, you can still rely on the order of execution. This applies to cases when `SELECT` comes from a subquery that uses `ORDER BY`. **Example** + show default.ck table result. ``` text @@ -29,7 +30,7 @@ show default.ck table result. Query: ``` sql -select id, groupArray(10)(name) from(select id,name from default.ck group by id,name order by id) group by id; +select id, groupArray(10)(name) from (select id, name from default.ck group by id, name order by id) group by id; ``` Result: