From 6bf63b5f860dffd545c1f981c33f309107404111 Mon Sep 17 00:00:00 2001 From: adela Date: Tue, 21 Apr 2026 22:11:29 +0200 Subject: [PATCH 1/3] docs: clarify SQL Editor Export re-executes the query MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Export button re-runs the SQL statement against the database instead of dumping the rows currently shown in the result panel — a reasonable first-time user assumption that the docs did not correct. Add a behavior note on run-queries.mdx and point the security page at it so the explanation lives in one place. Co-Authored-By: Claude Opus 4.7 (1M context) --- docs/security/database-permission/export.mdx | 2 +- docs/sql-editor/run-queries.mdx | 4 +++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/security/database-permission/export.mdx b/docs/security/database-permission/export.mdx index 84971e83..4f15708f 100644 --- a/docs/security/database-permission/export.mdx +++ b/docs/security/database-permission/export.mdx @@ -9,7 +9,7 @@ There are two ways to export data: ## Export directly from SQL Editor -As **SQL Editor User**, after you run a query, you can export the result by clicking **Export** button. The exported data still respects the masking policy to mask exported columns. +As **SQL Editor User**, after you run a query, you can export the result by clicking the **Export** button. See [Export data](/sql-editor/run-queries#export-data) for how Export behaves and what formats are supported. ![sql-editor](/content/docs/security/database-permission/export/sql-editor.webp) diff --git a/docs/sql-editor/run-queries.mdx b/docs/sql-editor/run-queries.mdx index c9740218..e26a08ad 100644 --- a/docs/sql-editor/run-queries.mdx +++ b/docs/sql-editor/run-queries.mdx @@ -58,7 +58,9 @@ The default query result size is **100 MB**. You can change it under the Workspa -The exported data still respects the [masking policy](/sql-editor/mask-data/) to mask exported columns if enforced. +**Export re-runs your SQL statement against the database** — it does not download the result set currently displayed in the tab. If the underlying data changed between the time you ran the query and the time you clicked **Export**, the exported rows will reflect the later state. To capture a specific point-in-time result set, copy the rows from the result panel or re-run the query immediately before exporting. + +The re-execution goes through the same row limit, data-source selection, and [masking policy](/sql-editor/mask-data/) as the original query, so exported columns are masked if the policy is enforced. From f2fc1c754c4421966f3199e4a44485b7636cb489 Mon Sep 17 00:00:00 2001 From: Adela Date: Wed, 22 Apr 2026 09:21:55 +0200 Subject: [PATCH 2/3] Update docs/security/database-permission/export.mdx Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/security/database-permission/export.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/security/database-permission/export.mdx b/docs/security/database-permission/export.mdx index 4f15708f..f0305ad8 100644 --- a/docs/security/database-permission/export.mdx +++ b/docs/security/database-permission/export.mdx @@ -9,7 +9,7 @@ There are two ways to export data: ## Export directly from SQL Editor -As **SQL Editor User**, after you run a query, you can export the result by clicking the **Export** button. See [Export data](/sql-editor/run-queries#export-data) for how Export behaves and what formats are supported. +As **SQL Editor User**, after you run a query, you can export the result by clicking the **Export** button. See [Export data](/sql-editor/run-queries#export-data) for how Export behaves. ![sql-editor](/content/docs/security/database-permission/export/sql-editor.webp) From d6adeca2ef353c820aeeee941ec2299cb39651bf Mon Sep 17 00:00:00 2001 From: Adela Date: Wed, 22 Apr 2026 09:24:48 +0200 Subject: [PATCH 3/3] Update docs/sql-editor/run-queries.mdx Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/sql-editor/run-queries.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sql-editor/run-queries.mdx b/docs/sql-editor/run-queries.mdx index e26a08ad..ad1cc028 100644 --- a/docs/sql-editor/run-queries.mdx +++ b/docs/sql-editor/run-queries.mdx @@ -60,7 +60,7 @@ The default query result size is **100 MB**. You can change it under the Workspa **Export re-runs your SQL statement against the database** — it does not download the result set currently displayed in the tab. If the underlying data changed between the time you ran the query and the time you clicked **Export**, the exported rows will reflect the later state. To capture a specific point-in-time result set, copy the rows from the result panel or re-run the query immediately before exporting. -The re-execution goes through the same row limit, data-source selection, and [masking policy](/sql-editor/mask-data/) as the original query, so exported columns are masked if the policy is enforced. +The re-execution goes through the same row limit, data-source selection, and [masking policy](/sql-editor/mask-data) as the original query, so exported columns are masked if the policy is enforced.