DBeaver
functionalImport DBeaver's data-sources.json with its folders and connection types, or export a data-sources.json DBeaver picks up.
DBeaver (Community and the paid editions) stores every connection of a project in data-sources.json, a JSON file DBeaver's own documentation describes. SQLly reads it, including folders, connection types and SSH tunnels, and writes one DBeaver loads as an extra connection file.
From DBeaver into SQLly
- Find the file in DBeaver's workspace:
~/Library/DBeaverData/workspace6/General/.dbeaver/data-sources.jsonon macOS,%APPDATA%\DBeaverData\workspace6\General\.dbeaver\data-sources.jsonon Windows,~/.local/share/DBeaverData/workspace6/General/.dbeaver/data-sources.jsonon Linux. (The.dbeaverfolder is hidden; on macOS press Cmd+Shift+. in the file chooser.) - Choose File → Import From Other Tools… and pick it.
- Kept - name, engine, host, port, database, user name, folder (as a project), read-only flag, connection type (Development, Test, Production become SQLly environments), and the SSH tunnel's host, port, user and key file. Connections configured by URL instead of host and port are read from the URL.
- Left behind - passwords (DBeaver encrypts them in
credentials-config.json), driver properties, bootstrap queries, and engines SQLly does not connect to, which are listed as skipped.
From SQLly into DBeaver
- Choose File → Export for Other Tools → DBeaver (data-sources.json)…, tick the connections, and save.
- Quit DBeaver, then put the file in the
.dbeaverfolder above under a new name that starts withdata-sources, such asdata-sources-sqlly.json. DBeaver loads everydata-sources*.jsonit finds there, so your existing connections are untouched. - Start DBeaver. The connections appear in their folders; DBeaver asks for each password on first connect.
The export covers PostgreSQL and its relatives, MySQL, MariaDB, SQL Server, SQLite, DuckDB and ClickHouse, with each connection's folder, environment type, read-only flag, user name and SSH tunnel. Oracle connections are skipped for now.