mirror of
https://github.com/dbeaver/cloudbeaver.git
synced 2026-04-25 05:36:14 +03:00
[GH-ISSUE #3499] Add a tag on queries launched by the export option #1272
Labels
No labels
AS
can't reproduce
can't reproduce
deployment
development
documentation
duplicate
duplicate
ee
enhancement
external
new driver
performance
pull-request
third party issue
wait for response
wait for review
wontfix
x:Oracle
x:cassandra
x:clickhouse
x:db2
x:duckdb
x:greenplum
x:h2
x:h2gis
x:hana
x:hive
x:intersystems
x:kyuubi
x:maria
x:mongo
x:mysql
x:postgresql
x:presto
x:sql server
x:sqlite
x:teradata
x:trino
xf:accessibility
xf:administration
xf:ai
xf:authentication
xf:aws
xf:commit-mode
xf:connection
xf:dark theme
xf:data editor
xf:datatransfer
xf:dba
xf:driver management
xf:erd
xf:filters
xf:i18n
xf:i18n
xf:installer
xf:json
xf:kerberos
xf:ldap
xf:local config
xf:log viewer
xf:metadata
xf:metadata editor
xf:navigator
xf:okta
xf:query manager
xf:resource manager
xf:scripts
xf:sql editor
xf:tasks
xf:ui/uix
xo: Firefox
xo:eclipse
xo:internet explorer
xo:macos
xp:major
xrn:internal
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cloudbeaver#1272
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @valentintraen on GitHub (Jun 3, 2025).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/3499
Is your feature request related to a problem? Please describe.
For security reasons, I check my entire MySQL fleet to dump data. The problem with Cloudbeaver is that a data export is a simple select *.
Describe the solution you'd like
Is it possible to add a comment to all export requests since they can be identified? For example SELECT /* cloudbeaver export */ ... like can mysqldump do it? And if it is possible, I would like the comment to be present by default, not that it is an option to activate.
Or, if it's simpler, use the integrated cloudbeaver logger to log who launched an export of what.
@EvgeniaBzzz commented on GitHub (Jun 13, 2025):
Hi @valentintraen
Thank you for your input on improving the application!
We'll add some kind of description in one of the future releases.
@valentintraen commented on GitHub (Feb 23, 2026):
Hi,
Any news ? :)
@EvgeniaBzzz commented on GitHub (Feb 25, 2026):
We will implement this, but I still can’t provide a date. Sometimes there simply isn’t enough time even for useful improvements 🙂
I will try to raise the priority.