JASP directly supports databases using Qt’s SQL plugin. You can connect to your database easily by entering connection details into a locally installed plugin. After connecting, you can enter a query and load the results as a dataset. A preview of the query results appears nearby, helping you fine-tune your queries. Queries can range from simple column selections to custom SQL or views.
Any query that returns a single table of data can be used. Additionally, you can set the database to refresh periodically after loading. Each time it refreshes, JASP checks for updates and automatically reruns analyses if necessary. By linking JASP to your production database, you can conveniently monitor important metrics in real-time through your own personalized dashboard.
According to Qt the following databases are supported:
- IBM DB2 (version 7.1 and above)
- Borland InterBase / Firebird
- MySQL or MariaDB (version 5.6 and above)
- Oracle Call Interface Driver (version 12.1 and above)
- Open Database Connectivity (ODBC) – Microsoft SQL Server and other ODBC-compliant databases
- PostgreSQL (versions 7.3 and above)
- SQLite version 3
- Mimer SQL (version 11 and above)
At the time of writing, JASP has not tested most database types, primarily because we don’t have direct access to those databases. Should any issues occur, we can offer assistance through our support contracts. Our support is limited by the database configurations that Qt itself supports, which varies with both the operating system and other local configurations.
According to Qt:
SQLite is the in-process database system with the best test coverage and support on all platforms. Oracle via OCI, PostgreSQL, and MySQL through either ODBC or a native driver are well-tested on Windows and Linux. The completeness of the support for other systems depends on the availability and quality of client libraries.