Shared connection export may expose credentials and unclear result‑set streaming
When a DBeaver connection is exported via the shared connections feature in DBeaver 23.0+, the resulting .dbeaver file contains plain‑text credentials, which can be unintentionally exposed if the file is committed to a public repository or shared via email. The ambiguity lies in how drivers handle result‑set retrieval: DBeaver may load the entire result set
dbeaver