docs: clarify SQL Editor Export re-executes the query#1089
Merged
adela-bytebase merged 3 commits intomainfrom Apr 22, 2026
Merged
docs: clarify SQL Editor Export re-executes the query#1089adela-bytebase merged 3 commits intomainfrom
adela-bytebase merged 3 commits intomainfrom
Conversation
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) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
There was a problem hiding this comment.
Pull request overview
Clarifies the SQL Editor Export behavior (it re-executes the SQL statement rather than downloading the currently displayed result set) and consolidates the explanation so there’s a single canonical documentation location.
Changes:
- Added an explicit callout in
run-queries.mdxexplaining that Export re-runs the SQL statement and may reflect newer database state. - Replaced the near-duplicate explanation in the database permission export doc with a link to the canonical section.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| docs/sql-editor/run-queries.mdx | Adds an Export behavior callout under “Export data” and reiterates masking/limits context. |
| docs/security/database-permission/export.mdx | Replaces duplicated Export explanation with a pointer link to the SQL Editor docs section. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
zchpeter
approved these changes
Apr 22, 2026
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
sql_service.go:839-890callsdoExport→queryRetry→ fresh statement execution; frontend atResultViewV1.vue:315-355sends the statement, not the fetched rows.docs/sql-editor/run-queries.mdx(the page users land on when asking "how does Export work?") and converted the near-duplicate paragraph indocs/security/database-permission/export.mdxinto a pointer link so the explanation has a single home.Test plan
/sql-editor/run-queries#export-data🤖 Generated with Claude Code