SQLly logoSQLly

DataGrip & JetBrains IDEs

functional

Import a project's dataSources.xml, or export your SQLly connections as one DataGrip, IntelliJ and the other JetBrains IDEs read.

DataGrip, IntelliJ IDEA Ultimate, PyCharm Professional, Rider and the other JetBrains IDEs with the Database tools plugin keep their data sources in dataSources.xml, one per project. Each entry holds a JDBC URL, and SQLly reads and writes those URLs for SQL Server, PostgreSQL and its relatives, MySQL, MariaDB, SQLite, DuckDB and ClickHouse. Oracle data sources are skipped for now.

From DataGrip into SQLly

  1. Find the file. In a project it is .idea/dataSources.xml. DataGrip's own default project lives in its settings folder: ~/Library/Application Support/JetBrains/DataGrip<version>/projects/default/.idea/ on macOS, %APPDATA%\JetBrains\DataGrip<version>\projects\default\.idea\ on Windows, and ~/.config/JetBrains/DataGrip<version>/projects/default/.idea/ on Linux.
  2. In SQLly choose File → Import From Other Tools… and pick it.
  3. Review the preview and click Import.

Each data source's name, engine, host, port and database come from its JDBC URL, and TLS settings in the URL (sslmode, encrypt, trustServerCertificate) are kept. A <user-name> in the file is imported too, but DataGrip usually keeps user names and SSH settings in a separate, per-user dataSources.local.xml and passwords in the IDE's keychain entry, so expect to type the user name and password the first time you connect.

From SQLly into DataGrip

  1. Choose File → Export for Other Tools → DataGrip (dataSources.xml)…, tick the connections, and save.
  2. Open the saved file in a text editor and copy everything inside <component> (the <data-source> elements).
  3. In DataGrip's Database Explorer press Paste (Cmd+V / Ctrl+V): DataGrip reads data source definitions from the clipboard and asks you to confirm each one. Alternatively, close the IDE and drop the file into a project's .idea folder.

The JDBC URL carries host, port, database and TLS mode, and each data source points at DataGrip's bundled driver for the engine, so DataGrip offers to download it if it is missing. SQLly's projects become DataGrip folders, and read-only connections stay read-only. User names and SSH tunnels are not written, because DataGrip keeps them in the per-user file rather than the shared one; add them in the data source's properties.